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 have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
We're seeing some weirdness with the GitHub Action. See how this Core PR created two bot comments that created two docs issues: this one and this one.
Expected Behavior
Only 1 issue gets generated per PR - this can be accomplished by checking that the label added by the labeled event was user docs
Steps To Reproduce
This is really a timing issue. In the case of the above PR, a label was added right after the PR was merged causing the workflow to trigger twice and since they ran simultaneously neither saw the comment the other generated in time to know to skip creating a new issue in the docs.getdbt.com repo.
Relevant log output
No response
Environment
- OS:
- Python:
- dbt:
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
[Bug] user docs autogenerated issues sometimes are duplicated
[CT-3171] [Bug] user docs autogenerated issues sometimes are duplicated
Sep 29, 2023
Is this a new bug in dbt-core?
Current Behavior
We're seeing some weirdness with the GitHub Action. See how this Core PR created two bot comments that created two docs issues: this one and this one.
Expected Behavior
Only 1 issue gets generated per PR - this can be accomplished by checking that the label added by the labeled event was
user docs
Steps To Reproduce
This is really a timing issue. In the case of the above PR, a label was added right after the PR was merged causing the workflow to trigger twice and since they ran simultaneously neither saw the comment the other generated in time to know to skip creating a new issue in the docs.getdbt.com repo.
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: