starred/oh-my-posh
1
0
Fork 0
mirror of https://github.com/JanDeDobbeleer/oh-my-posh.git synced 2026-08-24 10:14:12 -05:00
Code Issues Packages Projects Releases Wiki Activity

chore(markdown): use descriptive text

Browse Source
This commit is contained in:
Jan De Dobbeleer
2025-05-21 11:40:48 +02:00
committed by Jan De Dobbeleer
parent a02ee99f26
commit f3b568717f
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CODE_OF_CONDUCT.md
+2 -2
View File
@@ -115,13 +115,13 @@ the community.
## Attribution ## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available [here][version-2]. version 2.0, available [in the documentation][version-2].
Community Impact Guidelines were inspired by [Mozilla's code of conduct Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder][moz-div]. enforcement ladder][moz-div].
For answers to common questions about this code of conduct, see the [FAQ][faq]. For answers to common questions about this code of conduct, see the [FAQ][faq].
Translations are available [here][translations]. Translations are available [in the documentation][translations].
[homepage]: https://www.contributor-covenant.org [homepage]: https://www.contributor-covenant.org
[moz-div]: https://github.com/mozilla/diversity [moz-div]: https://github.com/mozilla/diversity
CONTRIBUTING.md
+1 -1
View File
@@ -10,7 +10,7 @@ can be a good starting point.
1. Ensure any dependencies or build artifacts are removed/ignored before creating a commit. 1. Ensure any dependencies or build artifacts are removed/ignored before creating a commit.
2. Commits follow the [conventional commits][cc] guidelines. 2. Commits follow the [conventional commits][cc] guidelines.
(You can [look up the supported *types*][cc-types] along with an explanation [here][cc-types]) (You can [look up the supported *types*][cc-types] along with an explanation [in the documentation][cc-types])
3. Update the documentation with details of changes to the functionality, this includes new segments 3. Update the documentation with details of changes to the functionality, this includes new segments
or core functionality. or core functionality.
4. Pull Requests are merged once all checks pass and a project maintainer has approved it. 4. Pull Requests are merged once all checks pass and a project maintainer has approved it.