1
0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 11:46:04 +00:00
Files
fep/scripts
silverpill 3fd575847b FEP-a4ed: Add types (#291)
This is a proposed solution for #175.

Required for #195

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/291
Reviewed-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
Reviewed-by: helge <helge@noreply.codeberg.org>
Co-authored-by: silverpill <silverpill@firemail.cc>
Co-committed-by: silverpill <silverpill@firemail.cc>
2025-02-05 15:41:57 +00:00
..
2025-02-05 15:41:57 +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