A likely change we have been discussing internally is that both issues and
pull requests at GitHub that are very stale---defined as a year old---could
get labeled ("tagged") and then closed. This may help with the somewhat
large amount of issues present.
If anybody has strong feeling about it, less us know. The current draft of
the corresponding YAML file is below. It has significantly more lenient time
windows than the default.
Thanks as always to anybody contributing to Rcpp with tips, tricks, comments,
issue tickets, bug reports, pull requests or otherwise.
Cheers, Dirk
# Mark stale issues and pull requests
# cf https://github.com/actions/stale
name: stale
on:
schedule:
- cron: "44 4 * * *"
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v3
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-label: 'no-issue-activity'
stale-pr-label: 'no-pr-activity'
days-before-stale: 365
days-before-close: 31
stale-issue-message: >
This issue is stale (365 days without activity) and will be closed
in 31 days unless new activity is seen. Please feel free to re-open
it is still a concern, possibly with additional data.
stale-pr-message: >
This pull request is is stale (365 days without activity) and will
be closed in 31 days unless new activity is seen. Please feel free
to open a new issue to discuss a fresh approach.
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
