remove draft documentation warnings
All checks were successful
/ test (pull_request) Successful in 25s
All checks were successful
/ test (pull_request) Successful in 25s
Resolves: forge/forge#530 Signed-off-by: Ryan Lerch <rlerch@redhat.com>
This commit is contained in:
parent
e4e7212ce4
commit
c4a833430d
18 changed files with 0 additions and 92 deletions
|
|
@ -1,10 +1,5 @@
|
|||
= Create a Custom Front Page for an Organization using a `.profile` Repository on Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
This guide demonstrates how to leverage the special `.profile` repository feature in https://forge.fedoraproject.org[Fedora Forge] to display a custom Markdown-based front page directly on your organization's main profile page. This allows for a richer and more informative landing experience for your organization.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= How to Create a New Organization in Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the steps required to create a new
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= How to Create a New Team in Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the steps required to create a new team within
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Email Notifications in Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document provides guidance on how to enable and configure email notifications in Fedora Forge. Email notifications help you stay informed about activities in repositories and organizations you're interested in.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Fedora Accounts Groups, Forge Organizations, and Team Naming Standards
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Overview
|
||||
|
||||
This document establishes the standard naming conventions for Fedora Accounts groups, Fedora Forge organizations, and team names used in Fedora Forge. Consistent naming helps administrators create appropriately named groups and organizations, and helps contributors understand what access different groups provide.
|
||||
|
|
|
|||
|
|
@ -2,11 +2,6 @@ include::partial$attributes.adoc[]
|
|||
|
||||
= Fedora Forge: Your Home for Fedora Collaboration
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
Welcome to Fedora Forge, the official home for Fedora teams, SIGs, and
|
||||
subprojects. Built on the open-source Forgejo platform, Fedora Forge is a
|
||||
dedicated space designed to streamline development and collaboration across the
|
||||
|
|
|
|||
|
|
@ -2,11 +2,6 @@ include::partial$attributes.adoc[]
|
|||
|
||||
= Setting Up Matrix Notifications for Your Repository
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document provides a comprehensive guide for setting up automated Matrix notifications for your Fedora Forge repository using the custom nonbot webhook. This allows you to receive real-time notifications about repository activities directly in your Matrix chat rooms.
|
||||
|
|
|
|||
|
|
@ -2,11 +2,6 @@ include::partial$attributes.adoc[]
|
|||
|
||||
= Migrating Issue Dependencies and Assignments from Pagure.io to Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document provides a comprehensive guide for using the `assign_and_depend.py` script to restore issue dependencies and assignments after migrating a project from Pagure.io to Fedora Forge. The built-in migrator does not handle this critical metadata, making this script an essential post-migration step.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= How to Migrate Repository from GitHub
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the steps required to migrate repositories from GitHub
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= How to Migrate Repository from GitLab
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the steps required to migrate repositories from GitLab
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Migrating from Pagure
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document provides an overview of migrating repositories from Pagure to Fedora Forge, with links to specific migration procedures based on your repository's content and requirements.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= How to Migrate Private Tickets from Pagure to a New Private Repository
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the steps required to migrate private/restricted issue tickets from a Pagure.io repository to a new private repository on Fedora Forge, ensuring the confidentiality of sensitive information while maintaining access control.
|
||||
|
|
|
|||
|
|
@ -1,12 +1,5 @@
|
|||
= How to Migrate Repository from Pagure
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:**
|
||||
This documentation is currently in draft form and may not be fully tested and correct.
|
||||
Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the steps required to migrate repositories from Pagure to Fedora Forge, ensuring proper transfer of repository contents, issue tickets, and pull requests to the new Forgejo-based platform.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Organizations and Teams Mapping for Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Overview
|
||||
|
||||
This document explains the relationship between Organizations and Teams in Fedora Forge, and how they map to concepts from Pagure.io. Understanding this mapping is crucial for teams migrating from Pagure.io to Fedora Forge.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Requesting a New Organization and/or Team in Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document outlines the standardized process for Fedora Project contributors
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Team Membership Management with Fedora Accounts
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Overview
|
||||
|
||||
This document explains how team membership is managed on Fedora Forge through Fedora Accounts (FAS) groups, and why we don't use Forgejo's built-in team management interface. Understanding this system is crucial for administrators and team members who need to manage team membership and access to repositories and organizations.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= How to Clone a Repository using HTTPS Authentication in Fedora Forge
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document provides a step-by-step guide on how to clone a repository from
|
||||
|
|
|
|||
|
|
@ -1,10 +1,5 @@
|
|||
= Webhook to Fedora Messaging for Forgejo
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
**DRAFT DOCUMENTATION:** This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies.
|
||||
====
|
||||
|
||||
== Purpose
|
||||
|
||||
This document explains how to quickly establish events from a Forgejo repository to be conveyed to the Fedora Messaging bus.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue