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

Support determining activity date from default branch #79

Merged
merged 3 commits into from
Feb 2, 2024

Conversation

anovadox
Copy link
Contributor

@anovadox anovadox commented Feb 1, 2024

Pull Request

New Staleness criteria: latest default_branch commit

Proposed Changes

Support determining activity date from default branch rather than most recent push to any branch

ACTIVITY_METHOD defaults to the current behavior: repo.pushed_at aka "pushed"

However, I think the most recent commit to the default branch (default_branch_updated) is another valid way of determining staleness/activity.

Our organization uses dependabot, which continues to open PRs and push commits to repositories which have not had any human contribution in more than a year.

With this change, we will easily be able to surface repositories that otherwise would be missed due to bot activity keeping them "fresh".

Readiness Checklist

Author/Contributor

  • If documentation is needed for this change, has that been included in this pull request
  • run make lint and fix any issues that you have introduced
  • run make test and ensure you have test coverage for the lines you are introducing

Reviewer

  • Label as either bug, documentation, enhancement, infrastructure, or breaking

…t recent push

activity_method defaults to the current behavior: repo.pushed_at

however, I think the most recent commit to the default branch
is another valid way of determining staleness/activity.

Our organization uses dependabot, which continues to open PRs
and push commits to repositories which have not had any human
contribution in more than a year.

With this change, we will easily be able to surface repositories
that otherwise would be missed due to bot activity keeping them
"fresh".
@zkoppert zkoppert added the enhancement New feature or request label Feb 1, 2024
README.md Outdated Show resolved Hide resolved
stale_repos.py Outdated Show resolved Hide resolved
@zkoppert
Copy link
Member

zkoppert commented Feb 1, 2024

Thanks for adding this enhancement @anovadox! Appreciate you adding this!

Co-authored-by: Zack Koppert <zkoppert@github.com>
Signed-off-by: Zack Koppert <zkoppert@github.com>
Copy link
Member

@zkoppert zkoppert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zkoppert zkoppert merged commit 5699b2b into github:main Feb 2, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants