issues: add new input issue-remove-labels-after-close (7d8e170), closes #859 When closing an issue, you can now remove some extra labels. This might be specifically handy if you want to remove the stale label to "clean" the closed issue.
prs: add new input pull-request-remove-labels-after-close (87e990b), closes #859 When closing a pull request, you can now remove some extra labels. This might be specifically handy if you want to remove the stale label to "clean" the closed pull request.
logs: improve the logger messages for the schemas checks (70f504d)
github: perform a GraphQL schematics validation before processing (f7b6df6), closes #855 This run will check every existing schema to ensure that queries and mutations are valid. If not, the processing will throw. This will help us ensure there is no issue and favor a fail-fast approach to fix potential issues ASAP.
issues: add new input issue-remove-labels-after-stale (65979f7), closes #858 This new input will let you remove some label(s) when the stale occur on issues.
prs: add new input pull-request-remove-labels-after-stale (f7890b1), closes #858 This new input will let you remove some label(s) when the stale occur on pull requests.
outputs: add new outputs removed-issues-labels-count and issues-labels-count (1b9ae0b), closes #858
outputs: add new outputs removed-pull-requests-labels-count and pull-requests-labels-count (ff3f686), closes #858
stats: add new stats about the removed issues labels (929efa7), closes #858
stats: add new stats about the removed pull requests labels (ccf4e1b), closes #858
website: add a new page to explain the migration from v1 to v2 (dea3137), closes #837
footer: change the link of the changelog (930afa0), closes #864 The new one will directly navigate to the docs changelog instead of the GitHub changelog.
inputs: reorder the added labels after close or stale (256463d), closes #839
close-reason: add new inputs issue-close-reason and pull-request-close-reason (d813b45), closes #779 Those inputs allow you to specify the reason for closing an item.
close-reason: The close reason will now be by default 'NOT_PLANNED' instead of 'COMPLETED' since it makes more sense. If you want to change the new default behavior, you can use these inputs: issue-close-reason: 'completed' pull-request-close-reason: 'completed'
issues: add new input issue-only-with-milestones (8083fa8), closes #808 This new input allows to only process issues containing at least one milestone.
prs: add new input pull-request-only-with-milestones (d9e240f), closes #808 This new input allows to only process pull requests containing at least one milestone.
issues: add new input issue-only-with-project-cards (2c4290e), closes #807 This new input allows to only process issues containing at least one project card.
prs: add new input pull-request-only-with-project-cards (2ff0851), closes #807 This new input allows to only process pull requests containing at least one project card.
issues: add new input issue-only-with-assignees (#772) (aeebf82), closes #313 This new input allows to only process issues containing at least one assignee.
prs: add new input pull-request-only-with-assignees (#775) (63d69b0), closes #313 This new input allows to only process pull requests containing at least one assignee.
inputs: add new inputs to only process items with specific assignees (2fc8bda), closes #559 Add the input issue-only-any-assignees. Add the input pull-request-only-any-assignees. You can use them to only process issues and PRs which have one of the specified assignee(s).
prs: add new input to ignore all milestones (a492a64), closes #520 Add the pull-request-ignore-all-milestones input. If a pull request has a milestone, it will be ignored from the processing.
issues: add new input to ignore all milestones (29d8724), closes #519 Add the issue-ignore-all-milestones input. If an issue has a milestone, it will be ignored from the processing.
input: add new inputs to ignore any project cards (#551) (ba79907) Add the issue-ignore-any-project-cards input. Add the pull-request-ignore-any-project-cards input. In addition of the existing input to ignore when a project card is present, now you can choose a white-list instead. Any item process that belong to those project cards will be ignored. Closes #165
milestone: add new input pull-request-only-any-milestones (6b9aa5a), closes #516 This new input will let you process only the pull requests that contains one of the specified milestone.
milestone: add new input issue-only-any-milestones (8d3fffd), closes #310 This new input will let you process only the issues that contains one of the specified milestone.
troubleshooting: add a new page to help troubleshooting (c67dc84) Including information about GitHub token missing permissions.
api-count: add info block to explain that a negative count disable the inputs (ac54236) Using -X for the API queries and mutations count will just disable the feaure.
github-token: add information about the required permissions (63fb15b) Also explain how the token is used under the hood.
logs: avoid showing a success log on error while fetching a label (26c07bf), closes #507 When a label could not be found, a log saying the label was loaded was display. It was misleading, and now it's no longer shown on error.
cache: cache the fetching of labels to reduce the amount of API calls (9b78d0d), closes #270 Every request to fetch a single label, like the stale one, will be cached for the whole workflow. This may reduce drastically the number of API calls made to GitHub. The limits related to your GitHub token will like this.
ui: change the brand name and the color scheme to follow Sonia style (3ce0536), closes #473 The Sonia corporation is a big joke, it's not a corporation and is only about open-source stuff. But having consistency between the different apps is cool, hence this change. I am not fond of the pink colour, but whatever I am just bad regarding the design.
prs: add new input pull-request-only-any-project-cards (ad82fd8), closes #416 This new input allow to only process prs belonging to specific projects. You can link your prs to a project card. Pass as a multi-line input the names of your projects. When this input is set, all prs without a project card will not be processed.
add @Sonia-corporation-bot as a contributor (c73b937)
readme: add a link to the changelog (ecc7c62), closes #414
need-help: add a new page to explain how to get some help (1d148e9), closes #415
annotations: add a new page to explain what are the annotations (c37a183), closes #448 Explain what to expect to find with the notices, warnings and errors.
blog: add new blog post to introduce the first inclusive input (f40b60f), closes #458
outputs: add tip about annotations (36c7378), closes #447
logs: properly count the number of processed items within all batches in the logs (8a17a18), closes #431 Only the first batch was taken into consideration. The information was lost during the recursion of batches processing.
annotations: format properly the errors annotations (13bcd6a), closes #422
annotations: format properly the warning annotations (469609c), closes #422
annotations: remove every existing notice annotations (3c3a2d5), closes #422 The logs were not static - including some variables - and were broken due to the colours.
issues: add new input issue-only-any-project-cards (8650e12), closes #312#412 This new input allow to only process issues belonging to specific projects. You can link your issues to a project card. Pass as a multi-line input the names of your projects. When this input is set, all issues without a project card will not be processed. Note: this is the first input of this genre, but may not be the last based on people needs!
prs: add new input pull-request-limit-api-mutations-count (5559871), closes #389 Before processing each pull request, the workflow will check if the input is enabled. If this is the case, the processing may stop if the statistics for mutations are higher than the limit.
issues: add new input issue-limit-api-mutations-count (14b034a), closes #376 Before processing each issue, the workflow will check if the input is enabled. If this is the case, the processing may stop if the statistics for mutations are higher than the limit.
issues: add new input issue-limit-api-queries-count (db5effb), closes #254 Before processing each issue, the workflow will check if the input is enabled. If this is the case, the processing may stop if the statistics for queries are higher than the limit.
prs: add new input pull-request-limit-api-queries-count (ee9a293), closes #254 Before processing each pull request, the workflow will check if the input is enabled. If this is the case, the processing may stop if the statistics for queries are higher than the limit.
statistics: always count the statistics even in dry-run (cbc41eb), closes #323 This will come particuly useful to know what is to be expected from the dry-run. Newcomers can really take advantage of this feature now.
labels: add new input to add extra labels after closing an item (f58a86b), closes #213 The input issue-add-labels-after-close and pull-request-add-labels-after-close were added. You can now define a list of extra labels to add when the processing close an item.
outputs: add draft pull requests count output (675faea) Add the draft-pull-requests-count output. Add a new statistic to count the number of pull requests converted to draft.
draft: add new input to convert a pull request to draft instead of stale (1efadfb), closes #275 The input pull-request-to-draft-instead-of-stale was added. When enabled, the processing will no longer stale. It will instead convert the pull request to a draft. No stale label added, no stale comment added nor extra labels added.
processing: add new input to enable or disable the processing (b57eac0), closes #277 Add the issue-processing and pull-request-processing inputs. When enabled, the processing occurs as expected. When disabled, the processing will be skipped.
stale: add in last the stale label to avoid removing the stale the next run (cb7257d) add the stale comment and the extra labels before adding the stale label this will avoid an issue with the update date being more recent than the stale label addition date
logs: add a log when a statistic is increased (3885885) Showing by how many the count was increased and also showing the new total count
stats: add a new statistic for the number of issue added labels (4805b65)
stats: add a new statistic for the number of PR added labels (ef5edab)
label: add new inputs to add extra labels after marking as stale (39433b0) Added the issue-add-labels-after-stale input Added the pull-request-add-labels-after-stale input
outputs: add new outputs for the count of added labels (397a712)
logs: add counts in the batches and processed items logs (2022cf0)
pull-request: add new input pull-request-delete-branch-after-close (cc53931) When a pull request is closed by the processing, if the option is enabled and the dry-run is disabled, the related branch will be removed A new output was also added to track the number of deleted pull request branches
processing: fix an issue with infinite batches processing (218f164) if the number of issues or pull requests to process was higher than 20, the processing was ending up in a infinity loop this was due to a missing parameter from the endpoint request "endCursor" which was not requested and so, leading to undefined value when the cursor is undefined, the first batch is processed hence the infinity loop
pr: add new inputs to support pull requests processing (ab8f8a0) this is the same implementation than the issues inputs from this point, issues and pull requests have the exact same options and features and this is closing the alpha state off this action