Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: Cleaning up old branches #1552

Closed
nschonni opened this issue Oct 1, 2020 · 11 comments
Closed

meta: Cleaning up old branches #1552

nschonni opened this issue Oct 1, 2020 · 11 comments
Assignees
Labels
Infrastructure Related to maintaining task force and repo operations, processes, systems, documentation

Comments

@nschonni
Copy link
Contributor

nschonni commented Oct 1, 2020

Here are some that I noticed looking at https://github.com/w3c/aria-practices/branches/all

  • the ones starting with "greenkeeper" can be removed now that the Dependabot move happened
  • branches that indicate they are for merged and/or closed PRs
  • branches that have "0" commits ahead of master. The
@nschonni
Copy link
Contributor Author

nschonni commented Mar 3, 2021

@mcking65 not sure if you're the best one to tackle this or if @jesdaigle / @zcorpan could do it (if you agree with the cleanup)

@zcorpan
Copy link
Member

zcorpan commented Apr 20, 2021

@nschonni yeah this seems like something we could do. Added to the backlog: https://github.com/w3c/aria-practices/projects/29

@zcorpan zcorpan added the Infrastructure Related to maintaining task force and repo operations, processes, systems, documentation label Apr 20, 2021
@zcorpan
Copy link
Member

zcorpan commented May 31, 2021

Removed:

I haven't removed branches that have no PRs or that are 0 commits ahead of main. We could probably delete more here, but I don't know if any given branch is one that should be preserved for some reason.

I would suggest ticking the checkbox "Automatically delete head branches" in GitHub settings for this repo, so that branches are removed automatically after PRs are merged.

https://docs.github.com/en/github/administering-a-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches

@zcorpan
Copy link
Member

zcorpan commented May 31, 2021

To remove branches locally in your clone that have been removed upstream, run:

git fetch --prune

@zcorpan
Copy link
Member

zcorpan commented Oct 26, 2021

@michael-n-cooper can you do this, please?:

I would suggest ticking the checkbox "Automatically delete head branches" in GitHub settings for this repo, so that branches are removed automatically after PRs are merged.

https://docs.github.com/en/github/administering-a-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches

@michael-n-cooper
Copy link
Member

@zcorpan done

@zcorpan
Copy link
Member

zcorpan commented Oct 29, 2021

Thank you, @michael-n-cooper!

I've removed the following branches for closed/merged PRs:

There are still a few pages of stale branches, without PRs or with open PRs, which I haven't removed. Again, not sure how to evaluate what to remove from these.

I'll say that this issue is fixed now.

@zcorpan zcorpan closed this as completed Oct 29, 2021
@nschonni
Copy link
Contributor Author

Thanks! I think there are a few more of the "0 ahead commits" branches likes that can be cleaned too
image

@nschonni
Copy link
Contributor Author

Few last Greenkeeper ones too
image

@zcorpan zcorpan reopened this Oct 30, 2021
@zcorpan
Copy link
Member

zcorpan commented Oct 30, 2021

0 ahead commits branches removed:

  • 1399
  • thermo
  • skipto
  • update-datepicker-javascript-code
  • 1007
  • 1037
  • tool
  • datepicker
  • wiki

Greekeeper:

  • greenkeeper/lint-staged-10.1.5

@zcorpan zcorpan closed this as completed Oct 30, 2021
@nschonni
Copy link
Contributor Author

Awesome! The rest of the non-PR'd stale branches would need some sort of review by the authors to see if there is anything useful, so I think this can remain close, unless you want to give homework at your next meeting 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Related to maintaining task force and repo operations, processes, systems, documentation
Projects
None yet
Development

No branches or pull requests

3 participants