Compass: GitLab integration branch variable

[Mac White]

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,

Mac

[Patrick Brady · Accepted solution]

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 https://developer.atlassian.com/cloud/compass/integrations/integrate-Compass-with-Gitlab/ 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 ;) )