https://code.forgejo.org/forgejo/release-scheduler will
use the release info derived from release-schedule.json:
* for each release that is not EOL and for which the cut date is in
the past, ensure that:
* a v* branch exists or create it from next
* a backport/label exists or create it
* for each backport/* labels, archive those that match a release that
is EOL
* all future release and EOL dates on Wednesdays
* v7 with EOL 2025
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/936
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Robert Wolff <mahlzahn@posteo.de>
Co-committed-by: Robert Wolff <mahlzahn@posteo.de>
- add a checklist to the release instructions
- use a pattern for push instead of an explicit list of branches
it was previously advisable to avoid conflicts when there was
no automated backports but it is no longer necessary
TODO:
- [x] comment out the `git push` once the website has submodules merged in
Fixes: https://codeberg.org/forgejo/docs/issues/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: https://codeberg.org/forgejo/docs/pulls/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>
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: https://codeberg.org/forgejo/docs/pulls/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>
