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've got an upstream repo integrated with Atlantis and teams fork this repo, create feature branches and create merge requests from fork to upstream. When I submit a merge quest on upstream repo, it automatically starts plan pipeline job and shows progress through interface as such and records that at the pipelines section.
Issue:
When a team member submits a merge request through fork repo, it also automatically starts plan pipeline job BUT does not show any progress through interface NOR records its execution at pipeline section.
Is this an expected behavior? Fork repo users in this case don't know Atlantis progress until output (from plan or apply job) pops out at the comments section.
The text was updated successfully, but these errors were encountered:
Environment:
Scenario:
I've got an upstream repo integrated with Atlantis and teams fork this repo, create feature branches and create merge requests from fork to upstream. When I submit a merge quest on upstream repo, it automatically starts plan pipeline job and shows progress through interface as such and records that at the pipelines section.
Issue:
When a team member submits a merge request through fork repo, it also automatically starts plan pipeline job BUT does not show any progress through interface NOR records its execution at pipeline section.
Is this an expected behavior? Fork repo users in this case don't know Atlantis progress until output (from plan or apply job) pops out at the comments section.
The text was updated successfully, but these errors were encountered: