It was previously possible to trigger the "Manage PRs" workflow for a pull request while a previous run for that PR is
already in process.
When that happens, it can result in erroneous bot comments. For example:
1. Workflow run is automatically triggered by a push.
2. Contributor does not notice this and comments a mention of the bot to trigger the workflow.
3. The first workflow run finds the PR is compliant and merges it.
4. The second workflow run finds the PR is compliant and attempts to merge it.
5. The second workflow run fails the merge (because it is already merged) and informs the contributor that there was a
merge conflict they must resolve.
6. The contributor is not able to resolve the non-existent conflict and is left wondering whether their submission was
successful.
The solution is to configure the "Manage PRs" workflow so that a workflow run in progress is canceled if the workflow is
triggered again for that PR. The "concurrency group" name is the PR number, so workflow runs in progress for other PRs
would not be affected.
* add TCA9555
* add RobTIllaart/SGP30
* Add AGS02MA
TVOC sensor - experimental library, use low speed I2C < 30 KHz, UNO does not really work as it cannot go that low.
* add MTP40C CO2 and air pressure sensor
* Add MTP40C CO2 and air pressure sensor
* Update repositories.txt
add experimental library - DAC8550
* Update repositories.txt
* Update repositories.txt
* add MINMAX library
Library to find peaks in a signal
* Update repositories.txt
