1
0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 03:35:52 +00:00
Files
fep/scripts/README.md
T
silverpill e928041c43 FEP-a4ed: Introduce trackingIssue metadata field (#284)
This is the first PR for issue https://codeberg.org/fediverse/fep/issues/185
Once this change is approved and merged, I will add `trackingIssue` to all existing proposals. After that `discussionsTo` can be used for solving https://codeberg.org/fediverse/fep/issues/274.

Reviewed-on: https://codeberg.org/fediverse/fep/pulls/284
Reviewed-by: Arnold Schrijver <circlebuilder@noreply.codeberg.org>
2024-05-17 19:33:25 +00:00

63 lines
1.3 KiB
Markdown

# 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](https://codeberg.org/fediverse/fep/pulls)
and note the slug.
```bash
python scripts/create_issue.py $SLUG
```
creates the tracking issue and updates the FEP with the information.
Then run
```bash
python 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.
Run
```bash
python scripts/create_topic.py $SLUG
```
and following the instructions to create a topic on SocialHub to discuss
the FEP.
Finally, add the link to the SocialHub topic to the tracking issue, created above.
## Configuration
Add a file `config.json` to the directory `scripts` with content
```json
{
"repo": "fep",
"owner": "fediverse",
"token": "CODEBERG_API_TOKEN"
}
```
The API token can be obtained by visiting [https://codeberg.org/user/settings/applications](https://codeberg.org/user/settings/applications) and generating one with scope `write:issue`.
## Setup for running pytest
Ensure dependencies (use a virtualenv)
```bash
pip install pytest
```
Check validity
```bash
pytest
```