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

add stale bot to housekeeping issues #272

Merged
merged 1 commit into from
Feb 16, 2021
Merged

add stale bot to housekeeping issues #272

merged 1 commit into from
Feb 16, 2021

Conversation

fabriciojs
Copy link
Member

Issue #253
⚠️ Break Change No

Description

Adding https://probot.github.io/apps/stale/ to mark/close old issues without recent activities.


Notes

Overall we should benefit from a cleaner/simpler issues dashboard for bugs, questions, and external proposals only whereas we shall manage the backlog out of the default GH issues.

@codecov
Copy link

codecov bot commented Feb 13, 2021

Codecov Report

Merging #272 (a79b95e) into master (8a8aec4) will decrease coverage by 0.07%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #272      +/-   ##
==========================================
- Coverage   88.55%   88.47%   -0.08%     
==========================================
  Files          67       67              
  Lines        2630     2630              
==========================================
- Hits         2329     2327       -2     
- Misses        278      281       +3     
+ Partials       23       22       -1     
Impacted Files Coverage Δ
cmd/shell/shell.go 85.43% <0.00%> (-1.95%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8a8aec4...e533592. Read the comment docs.

# Number of days of inactivity before a stale issue is closed
daysUntilClose: 15
# Issues with these labels will never be considered stale
exemptLabels:
Copy link
Contributor

Choose a reason for hiding this comment

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

should we add the 2.0 label here as well?

Copy link
Member Author

Choose a reason for hiding this comment

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

@danielsuguimoto I am thinking no... my sense is that we should move to have only short-lived issues here on GH, and move the broader roadmap/improvements to internal trackers. This is based on the stats that the /issues page is the second most viewed page after the repo homepage, and the overwhelming number of issues and different topics there does not help in the first impression for newcomers. This is a proposal though of course.

Copy link
Contributor

Choose a reason for hiding this comment

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

@fabriciojs okidoki!

@danielsuguimoto danielsuguimoto merged commit 94e402f into master Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants