1
0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 19:55:46 +00:00
Files
fep/scripts
Helge 854ef33092 Automate creating readme and tracking issue (#460)
Note at @fediverse/FEP-Editors

- Once this is merged please check it does the right thing.
- If you are ok with automating these things, I'll update the description of a facilitators role to just be checking and mergin
- finally, can we rename the codeberg group, I just addressed, to FEP-Facilitators

Final note: I already configured Woodpecker and the repository. This is to ensure that merging this pull request does not lead to a broken CI, second I might forget the steps ...

- [x] Force myself to document the automated process as a FEP

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/460
Reviewed-by: silverpill <silverpill@noreply.codeberg.org>
Co-authored-by: Helge <helge.krueger@gmail.com>
Co-committed-by: Helge <helge.krueger@gmail.com>
2025-01-20 10:24:00 +00:00
..
2023-07-16 07:43:02 +00:00
2023-07-16 07:43:02 +00:00
2024-11-15 11:22:01 +00:00

tools for fep facilitators

Please follow the steps in configuration before following "Merge a FEP".

Merge a FEP

Merge the Pull Request in https://codeberg.org/fediverse/fep/pulls and note the slug.

./scripts/create_issue.py $SLUG

creates the tracking issue and updates the FEP with the information. Then run

./scripts/create_readme.py

to update the table in README.md. You are now ready to commit the changes to the FEP (added trackingIssue to frontmatter) and README.md, added the new FEP.

Configuration

Add a file config.json to the directory scripts with content

{
  "repo": "fep",
  "owner": "fediverse",
  "token": "CODEBERG_API_TOKEN"
}

The API token can be obtained by visiting https://codeberg.org/user/settings/applications and generating one with scope write:issue.

Setup for running pytest

Ensure dependencies (use a virtualenv)

pip install pytest

Check validity

pytest