-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Please reopen #2628 #2805
Comments
Please don't raise a new issue for that, just comment on the referenced issue. IMHO it's fine to only use triggers with separate pipelines. When is only used to limit specific steps. |
I only opened a new issue because the comments there weren't being noticed. I'd open a thread on the forum, but I haven't had success there in the past either :) |
bot2-harness
pushed a commit
that referenced
this issue
Oct 11, 2024
* feat: [CODE-2312]: revert go-sdk changes in all places * feat: [CODE-2312]: revert go.mod changes * feat: [CODE-2312]: fresh reset * feat: [CODE-2312]: go.mod changes * feat: [CODE-2312]: address resourcename to commit.go * Merge branch 'main' into akp/CODE-2312 * feat: [CODE-2312]: address resourcename to commit.go * feat: [CODE-2312]: address resourcename to commit.go * feat: [CODE-2312]: address failure due to exceeding limit on resource labels * feat: [CODE-2312]: lint * feat: [CODE-2312]: MERGE * feat: [CODE-2312]: Update wire * feat: [CODE-2312]: update ui labels * feat: [CODE-2312]: update resource and action * feat: [CODE-2312]: Audit log new action : bypassed * feat: [CODE-2312]: audit log object update * Merge branch 'main' into akp/CODE-2312 * feat: [CODE-2312]: audit logging changes for commit, merge, create and delete branch * Merge branch 'main' into akp/CODE-2312 * Merge branch 'main' into akp/CODE-2312 * feat: [CODE-2312]: introduce parser and enclosing method * feat: [CODE-2312]: annotate error * feat: [CODE-2312]: name change and todo removal * feat: [CODE-2312]: Annotate errors * feat: [CODE-2232]: Branch Rules: UserGroup support: Create and List
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I commented on #2628 a few months ago, as the issue as described was never fully implemented.
Can it be reopened, or at least clarified?
The text was updated successfully, but these errors were encountered: