You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tend to create a PR very early to give my team and myself an overview of what I'm working on, but I don't need to run the build pipeline until I'm ready.
The "Pull Request Handler" workflow shouldn't trigger if a PR is still a draft, otherwise there's no way to prevent the workflow from running after creating a PR. If other users rely on status checks for drafts (not sure if that's the case, skipping status checks until the PR is ready for review is the default behavior), the AL Go settings could include a flag that adds a condition for the workflow after running a system file update.
The text was updated successfully, but these errors were encountered:
If a maintainer can point me in the right direction, I can make a pull request for this. I already did this for my fork, but I'm not sure where to exactly add the condition without accidentally skipping something else.
I tend to create a PR very early to give my team and myself an overview of what I'm working on, but I don't need to run the build pipeline until I'm ready.
The "Pull Request Handler" workflow shouldn't trigger if a PR is still a draft, otherwise there's no way to prevent the workflow from running after creating a PR. If other users rely on status checks for drafts (not sure if that's the case, skipping status checks until the PR is ready for review is the default behavior), the AL Go settings could include a flag that adds a condition for the workflow after running a system file update.
The text was updated successfully, but these errors were encountered: