mirror of
https://codeberg.org/fediverse/fep.git
synced 2026-08-05 11:46:04 +00:00
silverpill
f68a69fc79
This PR addresses https://codeberg.org/fediverse/fep/issues/686 and https://codeberg.org/fediverse/fep/issues/194 The "Type" column is added to all FEP lists, the value is either "informational" or "implementation (N)". Reviewed-on: https://codeberg.org/fediverse/fep/pulls/747 Reviewed-by: helge <helge@noreply.codeberg.org> Co-authored-by: silverpill <silverpill@firemail.cc> Co-committed-by: silverpill <silverpill@firemail.cc>
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