contributors.txt incorrectly refers to master branch
See original GitHub issuehttps://developer.mozilla.org/en-US/docs/Learn/CSS/First_steps/How_CSS_works/contributors.txt
# Contributors by commit history
https://github.com/mdn/content/commits/master/files/en-us/learn/css/first_steps/how_css_works/index.html
# Original Wiki contributors
warleyfdias
choudh70
jlbuckner
rachelandrew
chrisdavidmills
ExE-Boss
But there is no master branch, it should use main
.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Github problem: Git pushes to master branch, not main and ...
Go to my folder and run git init , git add . , git commit -m "first commit" , git remote add origin...
Read more >Error when creating a new branch for an empty repository #577
Hello, We are facing this error while trying to create a new branch for a new repository : github_branch.branch: Creating.
Read more >Use branch cleanup techniques - Manage Your Code Project ...
Go through your branches to see what branches need to be a part of the master branch. Use git merge and git rebase...
Read more >Git - Jenkins Plugins
It can poll, fetch, checkout, branch, list, merge, tag, and push ... repository using https protocol, no credentials, and the master branch.
Read more >Why GitHub renamed its master branch to main | TheServerSide
GitHub renamed the master branch to main for any Git repository, as it addresses cultural change like so many organizations that have nixed ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yep, it’s a caching issue. This is resolved.
Could be that the CDN cache is still warm. Try messing with the casing of the URL to bypass that.