bp/v1.20/meta into v1.20 A bunch of non-documentation stuff is being added to the repository which will need to be replicated on the release branch. This should not be merged until we are done adding this sort of stuff.
TODO: - [x] clone from website instead of caesar - [x] skip the proof of change commit Preview: https://forgejo.codeberg.page/@docs_pull_5/ This is a simplistic approach to get started with previews. It copies the website, moves the docs under `/forgejo-docs/{{ base branch }}`, create the website and publishes it for preview. No doubt the actual workflow will be different but that needs to be decided. * Added a WEBSITETOKEN secret created from the forgejo-website user. It is a token with write access to repositories. https://codeberg.org/forgejo/docs/settings/actions/secrets. Contrary to woodpecker it is not in an environment variable but will be replaced when inserting `${{ secrets.WEBSITETOKEN }}` somewhere * In the environment the variable was replaced CI_COMMIT_PULL_REQUEST → `${{ env.GITHUB_REF_NAME }}` * The preview is published at https://forgejo.codeberg.page/@docs_pull_N/ instead of https://forgejo.codeberg.page/@pull_N/ * The `$$` were replaced with `$` in the script because Forgejo Actions does not interpret `$` and therefore does not need escaping them to `$$` Reviewed-on: #5 Reviewed-by: Loïc Dachary <dachary@noreply.codeberg.org> Reviewed-by: Caesar Schinas <caesar@caesarschinas.com> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>
TODO: - [x] comment out the `git push` once the website has submodules merged in Fixes: #8 Additionally * Upgrade to node:20 * Exclude the README.md when copying to the preview * Allow forgejo-website to push to main on website  Preview: https://forgejo.codeberg.page/@docs_pull_9/ Reviewed-on: #9 Reviewed-by: Loïc Dachary <dachary@noreply.codeberg.org> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>
I will use this comment to keep a list of non-meta PRs that need to be backported after this is merged.
Does it matter if they're backported before or after this?
Not particularly. You may backport them now if you like, it will just require manual deployment and a rebase of this PR.
Refs: #3
(cherry picked from commit 5dde3a4231)
Preview ready: https://forgejo.codeberg.page/@docs_pull_15/
Depends on #6
Not resolved yet but I suppose it can be resolved later.
Archived
Archived
Archived
Archived
Archived
Archived
Archived
Archived
Archived
Archived
Archived
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?