Reviewer feedback from @lenkaseg noted that listing aarch64 as an option
in the architecture dropdown could imply it is available as a standard
offering, when it is still in an exploratory phase. Rather than removing
the option entirely, the description now clarifies that aarch64 runners
are not yet generally available and selecting the option expresses
interest for follow-up.
Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
Community members requesting Forgejo Actions runners for their
organizations previously had no standardized way to do so. Past requests
(issues #305, #331, #356, #372, #373, #402, #424, #480) varied from
single sentences to multi-paragraph freeform text, which sometimes
required follow-up to get missing details like architecture needs or
specific repositories.
This new template (`new_runner.yml`) provides a structured form that
captures the essential information maintainers need to provision runners
without follow-up: organization name, use case/justification,
architecture and resource requirements, and specific repositories.
Optional fields include sensible defaults so simple requests remain fast
to submit.
Design informed by analysis of all 8 historical runner requests and
aligned with existing template conventions (`new_organization.yml`).
Assisted-by: Claude Opus 4.6 (1M context)
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit fixes what I already started in PR #459 and commit
63f1084728, but I did not yet finish. I
used the wrong type and also did not make the checkbox options into
dictionaries. This is now done. I tested and validated that this looks
as expected.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit adds two new issue templates: a general issue template for
catch-all requests, as used by other teams; and a template to request a
new Fedora Forge organization, per the existing documentation:
The idea is that this issue template will encourage the correct format
for response without the person filing the issue to read the docs for
how to write a good request in the first place.
ref: https://docs.fedoraproject.org/en-US/forge-documentation/requesting_new_org_or_team/
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
- Convert from argparse to Click for modern CLI interface
- Add --production flag (defaults to staging) and --token parameter
- Add comprehensive setup documentation with dnf install instructions
- Skip users with non-@fedoraproject.org emails silently (no output)
- Skip users already marked with +fasnotfound@fedoraproject.org
- Treat FAS users with no emails as errors (should never happen)
- Improve statistics output with separate counters for different skip types
- Add environment variable support for FORGE_TOKEN
- Update script description to clarify it fixes migrator placeholders
This script addresses issue #191 by checking all potential Fedora Forge
organization names against Pagure.io to identify existing users with
conflicting names. Forgejo treats user and organization names the same
in some circumstances, which could cause migration issues.
This script automates a manual workaround for a known issue with the Fedora
Pagure migrator in Forgejo. When user accounts are created during migration
from pagure.io to Fedora Forge, they may not be properly enabled. Affected
users see an error stating they cannot create a new account and must contact
a system administrator. The only solution is for an administrator to visit
each user's edit page in the Forgejo UI and click "Save Changes". This script
iterates through all user accounts and performs that action automatically,
saving administrators time and effort.
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
