content: Fix Codeberg deployment article

This commit is contained in:
Rimas Kudelis 2025-06-17 09:08:15 +03:00 committed by GitHub
parent 5e3d849b8c
commit d1b2aad69e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -240,11 +240,11 @@ jobs:
name: Generated files name: Generated files
- name: Commit and push the website - name: Commit and push the website
run: | run: |
git config user.email codeberg-ci git config user.email codeberg-ci && \
&& git config user.name "Codeberg CI" git config user.name "Codeberg CI" && \
&& git add -v . git add -v . && \
&& git commit -v --allow-empty --message "Codeberg build for ${GITHUB_SHA}" git commit -v --allow-empty --message "Codeberg build for ${GITHUB_SHA}" && \
&& git push -v origin ${{ vars.TARGET_BRANCH }} git push -v origin ${{ vars.TARGET_BRANCH }}
``` ```
Once you commit one of the two files to your website source repository, you should see your first automated build firing up pretty soon. You can also trigger it manually by navigating to the **Actions** section of your repository web page, choosing **hugo.yaml** on the left and clicking on **Run workflow**. Once you commit one of the two files to your website source repository, you should see your first automated build firing up pretty soon. You can also trigger it manually by navigating to the **Actions** section of your repository web page, choosing **hugo.yaml** on the left and clicking on **Run workflow**.