Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Compass: GitLab integration branch variable

Hi Compass,

We have set a `COMPASS_BRANCH` variable to a value of `master`, but are failing to see our updates to our `compass.yml` file on the `master` branch populate was managed by `config-as-code`.  We would appreciate any help or tricks to get the component to update and find the relevant file. We have already checked to insure the project had been imported as part of the integration. Additionally, we used the copied Config-As-Code section of the component to create the initial `compass.yml` file. 

Thanks so much,


1 answer

1 accepted

3 votes
Answer accepted
Patrick Brady
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 29, 2022

Hello @Mac White, thanks for raising this issue! I tested it out myself as well and also saw this bug. I have checked out the code, found the issue, and just pushed out a bugfix to the application.

If you try again pushing a change to the file already in the `master` branch or pushing a new `compass.yml` file to that branch, it should now pick it up like it should. Let me know if you still encounter difficulties.

Also, for anyone else curious what this variable is for, we will update our documentation at to incude general instructions on how to use this COMPASS_BRANCH capability in GitLab to specify which branch to listen to for config-as-code changes. (and for build and merge events which will be released soon ;) ) 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events