Skip to content

docs(examples): add concurrency control to CI workflow examples#60

Open
stay-foolish-forever wants to merge 1 commit into
alibaba:mainfrom
stay-foolish-forever:doc/ci-example-concurrency-improvement
Open

docs(examples): add concurrency control to CI workflow examples#60
stay-foolish-forever wants to merge 1 commit into
alibaba:mainfrom
stay-foolish-forever:doc/ci-example-concurrency-improvement

Conversation

@stay-foolish-forever
Copy link
Copy Markdown
Contributor

Description

  • GitHub Actions: add concurrency group with cancel-in-progress to avoid redundant review runs on rapid pushes
  • GitLab CI: add interruptible and resource_group to cancel outdated review jobs when new commits are pushed to the same MR

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Refactoring (no functional changes)
  • Documentation update
  • CI / Build / Tooling

How Has This Been Tested?

  • make test passes locally
  • Manual testing (describe below)
    Tested under real Github projects

Checklist

  • My code follows the project's coding style (go fmt, go vet)
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the documentation accordingly (if applicable)
  • I have signed the CLA

Related Issues

Issue #58

- GitHub Actions: add concurrency group with cancel-in-progress to avoid
  redundant review runs on rapid pushes
- GitLab CI: add interruptible and resource_group to cancel outdated
  review jobs when new commits are pushed to the same MR
@stay-foolish-forever stay-foolish-forever marked this pull request as draft June 6, 2026 07:57
@stay-foolish-forever
Copy link
Copy Markdown
Contributor Author

I'm now performing some more tests on Gitlab, will merge if all tests under Gitlab pass.

@stay-foolish-forever stay-foolish-forever marked this pull request as ready for review June 6, 2026 10:16
@stay-foolish-forever
Copy link
Copy Markdown
Contributor Author

/open-code-review

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 6, 2026

OpenCodeReview: No comments generated. Looks good to me.

Copy link
Copy Markdown

@anupddas anupddas left a comment

Choose a reason for hiding this comment

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

Looks good overall. Good effort @stay-foolish-forever
Description is also clear and to the point.

Could we also update the README example to keep it consistent?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants