Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix concurrency groups in Readme #29021

Merged
merged 1 commit into from
Oct 16, 2023
Merged

Conversation

damccorm
Copy link
Contributor

Follow up on #28989


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@github-actions github-actions bot added the build label Oct 16, 2023
@damccorm
Copy link
Contributor Author

R: @Abacn @andreydevyatkin

@volatilemolotov
Copy link
Contributor

Missed the readme.

Looks good. Thanks

@github-actions
Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

@damccorm damccorm merged commit 1b50ebb into master Oct 16, 2023
3 checks passed
@damccorm damccorm deleted the users/damccorm/concurrency branch October 16, 2023 20:17
@@ -119,7 +119,7 @@ Concurrency groups are a way of making sure that no more than one Actions run is

```
concurrency:
group: '${{ github.workflow }} @ ${{ github.event.issue.number || github.event.pull_request.head.label || github.sha || github.head_ref || github.ref }}-${{ github.event.schedule || github.event.comment.id || github.event.sender.login}}'
group: '${{ github.workflow }} @ ${{ github.event.issue.number || github.sha || github.head_ref || github.ref }}-${{ github.event.schedule || github.event.comment.id || github.event.sender.login }}'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@damccorm This is actually not quite correct - we keep using the github.event.pull_request.head.label condition but only in case there is a pull_request_target event trigger. For instance, all PreCommit workflows have this event and the condition should be specified (e.g. https://github.com/apache/beam/blob/master/.github/workflows/beam_PreCommit_Go.yml#L50).
I think it makes sense to add a comment bellow describing this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andreydevyatkin would you mind putting up a PR to do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants