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

Idea: Customize the commit to pull compass.yml from

We currently use a number of different branching strategies across multiple products. Our goal would be to have the `compass.yml(s)` pulled from a source control system, BitBucket, GitHub, and eventually GitLab, be configurable by repository. 

For use we use `git-flow` and `trunk-based` branching strategies. In both scenarios, our `default` branch is not always as close to our current production branch, so for some audiences of Compass the information may be inaccurate. 


1 answer

1 accepted

0 votes
Answer accepted
Josh Campbell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 18, 2022

Hey Mac, you’ll be able to install the GitHub, Bitbucket, and/or GitLab (coming this year) integrations in the same Compass instance and use whichever you need on a per-component basis. As long as you have the integrations you need installed and configured, all you will need is a valid repository URL added to the component and Compass will take care of managing that relationship including watching for Compass.yaml (if present) changes in the appropriate VCS system. Does that help?

Regarding the branch, currently we’re only looking at the default branch with our Bitbucket and GitHub integrations and there isn’t a way to change/define that as a user. This is definitely a short term tradeoff we’ve made and I fully expect this won’t be the case forever.

This answer works. I would go a bit further as well and suggest that being able to see this at different "environments" would be interesting. For us production of course is important and will be our default, this currently is based more off of a tagging in git than branches. Of course this is not for all of our repositories, but for some. It would be interesting though to see the "status" of a component in Compass depending on the environment, for us that would be edge, stable, and production systems.


Like Josh Campbell likes this
Josh Campbell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 18, 2022

Ahh great feedback on environments, I suspect this would be beneficial to many others as well!! Keep it comin :) 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events