superfly / flyctl-actions

:octocat: GitHub Action that wraps the flyctl
Apache License 2.0
268 stars 34 forks source link

change repo primary branch to `main`? #42

Open isaacbowen opened 1 year ago

isaacbowen commented 1 year ago

https://www.theserverside.com/feature/Why-GitHub-renamed-its-master-branch-to-main

jsierles commented 1 year ago

This is good, but a lot of people are pinned to master already. Any idea what would happen if the name is changed?

isaacbowen commented 1 year ago

For sure:

If it's really important to keep that ref valid, you could wire up something to keep master synced to main too.

benthecarman commented 1 year ago

there's no reason to do this

pboling commented 4 months ago

If we expect the future to contain more projects than the past, and I sure hope it does, then it does make sense to do this.

In spite of anyone's misgivings, it is now the default on GitHub. So every time I see a master branch reference I am forced to wonder if the documentation is out of date, and go check. In fact - it is literally the reason I came to this page right now.

This adds many minutes of wasted time, every single time I see the term master. Multiply me by millions, and the aggregate cost to humanity is large. On the other hand the number of projects already using master is fixed at every point in time, so there is no better time to switch than now.

pboling commented 4 months ago

Additionally, there is a "keep-my-github-actions-up-to-date" dependabot task that should conceivably be made to handle this switch automatically, and send a PR to update. Not sure if it does as I only just started using it, but it would be a simple feature to add.

In .github/dependabot.yml

version: 2
updates:
  - package-ecosystem: 'npm'
    directory: '/'
    schedule:
      interval: 'daily'
    open-pull-requests-limit: 10
  - package-ecosystem: 'github-actions'
    directory: '/'
    schedule:
      interval: 'daily'