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

Periodically remove stale branches #132

Open
SHuang-Broad opened this issue May 26, 2020 · 4 comments
Open

Periodically remove stale branches #132

SHuang-Broad opened this issue May 26, 2020 · 4 comments
Assignees
Labels
refactor specifically related to engineering practices (sans testing) review-party things to be handled in the next review party

Comments

@SHuang-Broad
Copy link
Collaborator

SHuang-Broad commented May 26, 2020

I'll periodically check which branches Github deem as stale, and assign authors to either rebase or remove the branches.

@SHuang-Broad SHuang-Broad added the review-party things to be handled in the next review party label May 26, 2020
@kvg
Copy link
Collaborator

kvg commented May 26, 2020

Maybe we should consider auto-removing stale branches.

For the Dockstore branches, this is actually part of our release process to Terra - it's where all the WDL imports get rewritten to use full https URLs. Which is a bit unusual because these branches are deliberately generated, but not intended to ever be merged into master. I wonder if there's a way to auto-expire any branch that doesn't start with "dockstore_release_".

@SHuang-Broad
Copy link
Collaborator Author

Auto expiration might be hard for github: technically it's loosing data and I can almost hear the profanity from users....

Right now all PR branches will be auto-removed once merged. I guess it's OK to leave those that are intended to serve a quick purpose, as long as we don't become GATK-like (32 pages of stale branches....)

@SHuang-Broad SHuang-Broad self-assigned this Jul 20, 2020
@SHuang-Broad
Copy link
Collaborator Author

SHuang-Broad commented Jul 20, 2020

Assigning authors


@kvg

  • kvg_autopipe
  • kvg_ont_plasmodium
  • kvg_beryl
  • kvg_beryl_realign
  • kvg_hgsvc2
  • kvg_variant_metrics
  • kvg_dv_fixes
  • kvg_lower_canu_cov
  • kvg_c3poa_patch

@jonn-smith

  • jts_margin_polish_helen
  • jts_scripts_and_wdls_1

@ericsong

  • canu
  • songe/broken-shasta-example
  • songe/ontpf-assembly
  • songe/shasta-assembly

@SHuang-Broad SHuang-Broad pinned this issue Jul 22, 2020
@kvg kvg self-assigned this Aug 17, 2020
@kvg
Copy link
Collaborator

kvg commented Aug 17, 2020

@kvg to investigate rewriting the release process to not rewrite imports anymore, cutting down on number of branches we need to keep around.

@SHuang-Broad SHuang-Broad added the refactor specifically related to engineering practices (sans testing) label Oct 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor specifically related to engineering practices (sans testing) review-party things to be handled in the next review party
Projects
None yet
Development

No branches or pull requests

2 participants