As we (Quality team) were doing our migrations to Forge, we came
up with a checklist and some supplemental migration tools. This
adds a slightly tweaked version of the checklist to the migration
doc as we think it will be helpful for all other teams.
See quality/tickets#836
for the original.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
- Add Option A (simple store) and Option B (libsecret) for credential helpers
- Recommend libsecret for secure storage in GNOME Keyring/KDE Wallet
- Add installation and configuration instructions for libsecret
- Clarify that Access Token should be used as password, not FAS password
- Add link to official Git credentials documentation
Fixes the documentation clarifying what permissions to give the key.
also added note about how we can run the script for you using the
forgebot account.
Fixes #282
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
The naming standards document is more relevant for users who are requesting
organizations and teams, rather than being admin-specific documentation.
Placed it after the 'Requesting a New Organization and/or Team' document
for better logical flow.
Changed example organization name from 'myawesomesig' to 'infra' to be
consistent with naming standards that discourage using '-sig' suffix in
organization names.
Updated all example text to use 'Fedora Infrastructure Team' as a more
realistic and clear example throughout the documentation.
Fixes: forge/forge#271
Reported-by: Gordon Messmer
The migrator bug that prevented users from being created properly has been
fixed. The workaround documentation and references are no longer needed.
Changes:
- Removed known_issue_cannot_create_user.adoc
- Removed reference from nav.adoc
- Removed reference from migration/pagure.adoc
- Change authenticated user from 'ryanlerch' to 'adminuser'
- Replace real usernames with fictional ones: dudemcpants, testermctesterson, fergieforge
- Use example.com and example.org domains instead of real email addresses
- Maintain educational value while protecting user privacy
- Sample still demonstrates all key script scenarios (successful updates, fasnotfound cases)
- Document how team membership is managed through Fedora Accounts groups
- Explain why Forgejo UI team management is not used
- Provide step-by-step instructions for managing team membership
- Include important note about logout/login requirement for changes
- Add to User Documentation navigation
- Document relationship between Organizations and Teams in Fedora Forge
- Explain mapping from Pagure.io concepts to Forgejo structure
- Provide Rust organization migration example with standard FAS group naming
- Link to FAS Group Naming Standards for exception cases
- Add to User Documentation navigation
- Document Fedora Accounts groups, Forge organizations, and team naming
- Explain that owners team is mandatory (Forgejo requirement), not specifically the Fedora Accounts group
- Document flexible team naming with examples (docs teams: quick-docs-writers, etc.)
- Document organization naming (no fedora- prefix, no -sig suffix)
- Document examples for council, releng, and docs organizations
- Document exception cases for reusing existing groups like council
Documents issue #139 where adding repository issues to organization-level projects fails silently when the Projects unit is disabled at the repository level. Includes problem description, symptoms, root cause, workaround steps, and upstream status with links to bug report and fix PR.
Comprehensive guide covering:
- Creating issue templates with YAML front matter
- Creating pull request templates (single template per repo)
- Issue template configuration with blank_issues_enabled and contact_links
- Form-based YAML templates with link to official docs
- Troubleshooting common template issues
- Created shared include file: partials/access_fedora_forge_migration_tool.adoc
- Updated pagure_repository.adoc to use shared section via include
- Updated pagure_private_tickets.adoc to use shared section via include
- Removed outdated steps from private tickets document
- Both documents now use consistent, up-to-date migration tool access steps
This eliminates code duplication and ensures both migration documents
stay in sync when the shared steps need to be updated.
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
- Renamed migration_pagure_08.png to pagure_migration_new_migration_button.png
- Renamed migration_pagure_09.png to pagure_migration_select_pagure_source.png
- Renamed migration_pagure_10.png to pagure_migration_form_filled.png
- Renamed migration_pagure_11.png to pagure_migration_start_migration_button.png
- Renamed migration_pagure_12.png to pagure_migration_completion_success.png
- Cropped screenshots to remove empty space and unneeded bloat for cleaner documentation
Updated references in both pagure_repository.adoc and pagure_private_tickets.adoc
to use the new descriptive filenames that clearly indicate image content.
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
- Fix xref:pagure_repository.adoc to xref:migration/pagure_repository.adoc
- Fix xref:pagure_private_tickets.adoc to xref:migration/pagure_private_tickets.adoc
- Fix xref:github.adoc to xref:migration/github.adoc
- Fix xref:gitlab.adoc to xref:migration/gitlab.adoc
Resolves AsciiDoc build errors for missing xref targets in pagure.adoc
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
- Add consistent draft warning to all non-migration documentation
- Warn users that documentation is in draft form and may not be fully tested
- Encourage users to verify procedures before use
- Request feedback on issues or inaccuracies
- Ensure consistent user experience across all documentation
This provides transparency about the current development status of the
Fedora Forge documentation and helps manage user expectations.
- Split original Pagure migration doc into three documents:
- Overview document with migration options
- Standard repository migration guide
- Private tickets migration guide
- Add draft documentation warnings to all migration docs
- Correct API key usage warnings (only needed for private tickets)
- Update navigation to group Pagure migration docs together
- Move issue dependencies migration under Pagure subsection
- Crop screenshots to remove unnecessary content
- Improve procedure formatting with headings and summaries
- Specify Pagure.io instance name for clarity
- Streamline API key creation steps with better instructions
- Fix heading levels across all documents (level 1 titles, level 2 sections)
- Convert procedure ordered lists to headings for better navigation
- Add procedure summaries to admin documentation
- Simplify ordered list formatting by removing unnecessary * formatting
- Update navigation to include new Pagure migration sub-documents
This improves consistency and usability across all Fedora Forge documentation.
