starred/definitive-opensource-mustbeperfect
1
0
Fork 0
mirror of https://github.com/mustbeperfect/definitive-opensource.git synced 2026-04-17 15:43:26 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated version and fixed issues in contributing document

Browse Source
This commit is contained in:
Lucas
2025-11-12 10:22:26 -08:00
parent f694092f93
commit 529a3400f7
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.github/CONTRIBUTING.md vendored
View File

@@ -9,7 +9,7 @@ Please note that this project is released with a [Contributor Code of Conduct](C
- [How To Contribute](how-to-contribute)
## A Quick Note
The scale of what this project is attempting to accomplish is one that can only be done collectively. All contributions are highly valued. For submission guidelines on projects, please consult the [submission guidelines](GUIDELINES.md)
The scale of what this project is attempting to accomplish is one that can only be done collectively. All contributions are highly valued. For submission guidelines on projects, please consult the [submission guidelines](/.github/GUIDELINES.md)
>[!IMPORTANT]
>When possible, please edit the file directly and start a pull request instead of raising an issue. DO NOT EDIT THE README. Edit applications.json.
@@ -19,7 +19,7 @@ To establish uniformity accross the project, please adhere to these conventions.
- Use the project's official name, not the repository name. Repository names often use lowercase and place dashes in place of spaces. Fallback to **Title Casing** if capitalization is not clear.
- For projects with multiple repositories (EX: one for IOS, Windows, etc) link the repository with the most stars.
- Do not put in a description unless the repo description is inadequate or non-existent, in which case fall back to the organization, their website, or the repo's README. **Do not write your own description, only use text from official sources of the project, and do not modify (EX: shorten) their description.** If you use a custom description make sure to put in the `custom-description` flag so that the stat updator script doesn't overide it.
- For tags, do not use the emoji. Go to [tags.json](source/data/static/tags.json) and find the id for the tag. Our script will generate it's corresponding emoji when it builds the README.
- For tags, do not use the emoji. Go to [tags.json](/source/data/static/tags.json) and find the id for the tag. Our script will generate it's corresponding emoji when it builds the README.
## How To Contribute
[How to create a pull request.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
@@ -49,7 +49,7 @@ Add the `name`, `repo_url`, `tags`, `platform(s)`, and `category`. Everything el
## Guidelines
- Check the archive, the backlog, and duplicates
- Make sure the category is fitting
- The pull request and commit should have concise and descriptive titles
- The pull request and commit should be simple. EX: Added `Name` to `category`
- One pull request per new addition
- If a project is in the grey zone for submission guidelines, include why it should be included.
- Proposals for new categories or the re-organization of existing categories must be discussed and approved via an issue prior to the pull request

0
source/components/crossheader.md
View File

2
source/scripts/generation/mainheader_generator.py
View File

@@ -10,7 +10,7 @@ def generate_mainheader():
header_content = f"""
<table align="center">
<tr>
<td>🌍 v0.6.3-beta</td>
<td>🌍 v0.7.4-beta</td>
</tr>
</table>