* Try merging with the queue
* Provide github token
* Fix syntax
* Get GITHUB_TOKEN from vault
* Add the PR label
* Wait for the new PR to merge
* Fix working dir
* Inline the script
* Checkout master
* Install python for slack notifications
* Fix logging
* install rspec-tools
* Log actual PR-merge status
* Final adjustments
* Set check interval to 20 seconds
* Test failure
* Fix pr close command
* Revert "Test failure"
This reverts commit c3c2b845feaa047a62ef19fb34c805bf3ef7a23f.
* Update .github/workflows/update_coverage.yml
---------
Co-authored-by: Fred Tingaud <95592999+frederic-tingaud-sonarsource@users.noreply.github.com>
* Try merging with the queue
* Provide github token
* Fix syntax
* Get GITHUB_TOKEN from vault
* Add the PR label
* update coverage information
---------
Co-authored-by: Arseniy Zaostrovnykh <necto.ne@gmail.com>
Co-authored-by: SonarTech <sonartech@sonarsource.com>
The previous change to the task 'Push the updated coverage to master' made it passthrough because it used {{ as part of the condition, which seems to be forbidden.
Changing the condition to what we usually use to check default_branch in other workflow scripts throughout our repositories.
* Fix SQ issue Unexpected string concatenation
* Allow testing of the coverage update workflow by checking out all
branches and referencing the SHA of the triggering event
* Fix repository url for coverage update
* Add a manual trigger for coverage update
The frontend SQ analysis frequently fails during the night likely because
it runs soon after SQ is redeployed. Move the update_coverage job 2h
later to avoid that.
Following Node12's deprecation by GitHub, we started getting the
following message:
```
create_new_rule
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
```
From the doc of these actions, it looks like just upgrading the versions
should work transparently.
`update_coverage` action used to wait for `validate_asciidoc` to succeed as the task that takes the longest. After #782 is merged as f21f23b9860c10d4effb00b6022917bc28e02e61 it is no longer the case. This change introduces `all_required_checks` task that depends on all checks required for a PR to be merged, thus providing a single point that is known to succeed last and can be safely waited upon.
