Switching default branch seems to have broken things
See original GitHub issueGreetings folks, and thank you for a lovely GitHub Action! A few weeks ago I switched the default branch in my project from master
to main
. Everything with the transition seems to be working, except for code coverage.
My usage of the GitHub Action is pretty basic: https://github.com/JustinBeckwith/linkinator/blob/main/.github/workflows/ci.yaml#L31
Yet the dashboard, it shows nothing: https://app.codecov.io/gh/JustinBeckwith/linkinator/
This used to work perfectly fine when I was on the master
branch, so I’m fairly certain it has something to do with that transition. Forgive me if this isn’t the right place to post, but it felt like a good place to start 😃
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
switching default the branch causes the project to break
We are testing out Config as Code, and we had to change the default branch. However, that seems to break the project, and...
Read more >Broken branch in git, fatal: your current branch appears to be ...
If it happens, go to the directories .git/logs/refs/heads/<name> and .git/refs/heads/<name> , and you'll see your branch is now a folder with a ......
Read more >I just noticed github changed the default branch from master to ...
But yeah, I can understand the master/slave renami g of things like Redis a lot more than the master to main change.
Read more >support changing the default wiki branch name - GitLab
Right now it's possible for new wikis to inherit the default branch name, as explained in Configure a default branch for your wiki...
Read more >Easily rename your Git default branch from master to main
Now I just need to change my default branch in my GitHub settings for my ... The last thing to think about is...
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 Free
Top 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
@helpermethod I made some changes to the GitHub Action that should make this unnecessary now.
@thomasrockhu Is this still needed? Somehow I never had a problem with fetch-depth
1
.