iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/.github/workflows/feature-requests.yml

16 lines
402 B
YAML
Raw Normal View History

ci: introduce action implementing feature request prioritization process (#41975) Enable a GitHub action that implements our new feature request [process](https://github.com/angular/angular/blob/ce8e011a9f7c6bac94292d632b0cc8822f710a66/docs/GITHUB_PROCESS.md#feature-request-process). As a prerequisite, we need to create the following labels: - `in backlog` - `votes required` - `under consideration` - `insufficient votes` The bot will also use the existing `feature` label to identify feature requests. With its current configuration, we need to kick the process off manually. We currently also have a limit, meaning the bot will process only 50 feature requests before it exits. Additionally, now the bot will not close issues, it'll just comment on them and if they have an insufficient number of votes, the bot will label them with `insufficient votes`. On the next iteration, we can: - Expand the limit from 50 to infinity (removing the option from the yml file) - Set a cron configuration to kick off the bot automatically - Enable autoclose by setting the `close-when-no-sufficient-votes` to `true` PR Close #41975
2021-05-06 19:49:59 -04:00
name: Feature request triage bot
ci: update the github feature request process action and run on cron (#42337) - Update to the latest hash - Set the limit to 100 feature requests - Run daily at 2pm PR Close #42337
2021-05-25 19:36:55 -04:00
on:
schedule:
# Run at 14:00 every day
- cron: '0 14 * * *'
ci: introduce action implementing feature request prioritization process (#41975) Enable a GitHub action that implements our new feature request [process](https://github.com/angular/angular/blob/ce8e011a9f7c6bac94292d632b0cc8822f710a66/docs/GITHUB_PROCESS.md#feature-request-process). As a prerequisite, we need to create the following labels: - `in backlog` - `votes required` - `under consideration` - `insufficient votes` The bot will also use the existing `feature` label to identify feature requests. With its current configuration, we need to kick the process off manually. We currently also have a limit, meaning the bot will process only 50 feature requests before it exits. Additionally, now the bot will not close issues, it'll just comment on them and if they have an insufficient number of votes, the bot will label them with `insufficient votes`. On the next iteration, we can: - Expand the limit from 50 to infinity (removing the option from the yml file) - Set a cron configuration to kick off the bot automatically - Enable autoclose by setting the `close-when-no-sufficient-votes` to `true` PR Close #41975
2021-05-06 19:49:59 -04:00
jobs:
feature_triage:
if: github.repository == 'angular/angular'
runs-on: ubuntu-latest
steps:
ci: update the github feature request process action and run on cron (#42337) - Update to the latest hash - Set the limit to 100 feature requests - Run daily at 2pm PR Close #42337
2021-05-25 19:36:55 -04:00
- uses: angular/dev-infra/github-actions/feature-request@a3fb5e24b659411f1163461a778a1fa79e119d2f
ci: introduce action implementing feature request prioritization process (#41975) Enable a GitHub action that implements our new feature request [process](https://github.com/angular/angular/blob/ce8e011a9f7c6bac94292d632b0cc8822f710a66/docs/GITHUB_PROCESS.md#feature-request-process). As a prerequisite, we need to create the following labels: - `in backlog` - `votes required` - `under consideration` - `insufficient votes` The bot will also use the existing `feature` label to identify feature requests. With its current configuration, we need to kick the process off manually. We currently also have a limit, meaning the bot will process only 50 feature requests before it exits. Additionally, now the bot will not close issues, it'll just comment on them and if they have an insufficient number of votes, the bot will label them with `insufficient votes`. On the next iteration, we can: - Expand the limit from 50 to infinity (removing the option from the yml file) - Set a cron configuration to kick off the bot automatically - Enable autoclose by setting the `close-when-no-sufficient-votes` to `true` PR Close #41975
2021-05-06 19:49:59 -04:00
with:
ci: update to latest feature request triage bot commit (#42084) Update to the latest feature request triage bot commit to use the angular robot github app instead of a token directly. PR Close #42084
2021-05-13 16:09:09 -04:00
angular-robot-key: ${{ secrets.ANGULAR_ROBOT_PRIVATE_KEY }}