32c187e5bb
Followup to https://codeberg.org/forgejo/forgejo/pulls/8513 More at https://codeberg.org/fedora/forgejo-deployment/issues/186 Related: https://codeberg.org/forgejo/forgejo/pulls/8513#issuecomment-6075304, https://codeberg.org/forgejo/forgejo/pulls/8513/files#issuecomment-6075322 Previously, users were getting confused about the token/private issues behavior in the Pagure migrator, as the UI didn't clearly explain the two-repository workflow or the security implications of using an API token. This commit updates the Pagure migration template to make the behavior clearer by: - Adding a collapsible details section for private issues functionality to reduce UI clutter since this feature is not expected to be used frequently - Replacing inline help text with proper Fomantic UI message boxes (blue info for description, red warning for security notice) - Providing clear explanations of the two-step migration process (public content first, then private issues archive) - Adding prominent security warnings about repository visibility when importing private content The private issues section is now hidden by default in a collapsible element, making the standard migration flow cleaner while still providing access to advanced functionality when needed. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9502 Reviewed-by: 0ko <0ko@noreply.codeberg.org> Co-authored-by: Ryan Lerch <rlerch@redhat.com> Co-committed-by: Ryan Lerch <rlerch@redhat.com> |
||
|---|---|---|
| .. | ||
| gitignore | ||
| label | ||
| license | ||
| locale | ||
| locale_next | ||
| readme | ||
| locale_readme.md | ||