Greasy Fork

Hello,

I just like to know if your script is for those who have repositories on GitHub or for everyone please ?

Because after installing your script, no labels are displayed on my side for example here :
-> https://github.com/refined-github/refined-github/commits/main/
-> https://github.com/Tampermonkey/tampermonkey/commits/master/

Thank you for your answer.

Google Chrome and Mozilla Firefox Browsers with Tampermonkey or Violentmonkey

Hi, this script should work for anyone using GitHub repositories, whether it's your own or someone else's. However, the script will only display labels for repositories that follow a Git commit message convention.

See: -> https://github.com/refined-github/sandbox/commits/conventional-commits/ -> https://github.com/nazdridoy/ngpt/commits/main/ -> https://github.com/nazdridoy/kokoro-tts/commits/main -> https://github.com/conventional-changelog/standard-version/commits

Example Commit Formats Here are some examples of how to format your commits to get the labels:

# Basic format
feat: add new login functionality
fix: resolve authentication bug
docs: update API documentation

# With scope
feat(auth): implement OAuth2 login
fix(api): handle rate limiting errors
feat!(auth): implement breaking change in auth
refactor!(parser): rewrite parser logic (breaking change)
docs(readme): add installation guide
style(button): improve hover effects
refactor(service): clean up user service code
perf(db): optimize database queries
test(auth): add unit tests for auth service

Thank you very much because I understand better :-)

I'm not an advanced user yet, but I would like to know how to know which repository follows a Git commit message convention please ?
It's very new to me, but I'm very interested to know more.

You are welcome,

You can usually tell by looking at the repo's documentation. Check the CONTRIBUTING.md or README for a "Commit Message Guidelines" section; often, these will reference Conventional Commits, Angular's style, etc. Many projects also include a commitlint.config.js or Git hook in .husky/ to enforce commit message conventions, or even a badge in the README. If none of these appear, the project probably isn't enforcing a formal convention. However, keep in mind that commit message convention is still just a convention; some developers follow it, and some don't.

Very well and again many thanks for all this ;-)