| |
@@ -16,7 +16,7 @@
|
| |
|
| |
== Content
|
| |
|
| |
- Teams should list the following information in the format specified by https://pagure.io/Fedora-Council/council-docs/blob/master/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[the template]:
|
| |
+ Teams should list the following information in the format specified by https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[the template]:
|
| |
|
| |
* Team name
|
| |
* Team summary
|
| |
@@ -51,7 +51,7 @@
|
| |
The directory requires a file that contains the information about the team.
|
| |
The suggested naming convention is `NAME_team_info.adoc`, but any valid file name is acceptable.
|
| |
The file may be stored in the team's own documentation repository or in the https://pagure.io/Fedora-Council/council-docs/[council-docs repository].
|
| |
- See the https://pagure.io/Fedora-Council/council-docs/blob/master/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[example template] for format and structure.
|
| |
+ See the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[example template] for format and structure.
|
| |
|
| |
=== Rendering the directory
|
| |
|
| |
@@ -60,5 +60,5 @@
|
| |
|
| |
=== Reusing the data on team pages
|
| |
|
| |
- Teams can include their `NAME_team_info.adoc` file on their page(s), and then use `{team_name}`, `{team_summary}` etc. anywhere on the page.
|
| |
+ Teams can include their `NAME_team_info.adoc` file on their page(s), and then use `{team_name}`, `{team_summary}` etc. anywhere on the page.
|
| |
|
| |
Last month, GitHub switched their default git branch from
master
tomain
. So, if GitHub is doing it for their millions and millions ofrepos and users, there are few good reasons not to for this repo.
https://github.com/github/renaming
This commit changes all references of
master
tomain
in the Antorasite configuration. This commit is already pushed to a git branch,
main
, on the council-docs repo. But this commit will be opened as aPull Request to the
master
branch.Do not merge without coordinating on the fedora-docs/docs-fp-o PR.
If the builder is still configured to build onto
master
, well, thatobviously will not work. Please coordinate these changes simultaneously.
Closes #86. cc: @mattdm