Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always use .dorpsgek.yml of main (master) branch #7

Closed
TrueBrain opened this issue Sep 16, 2019 · 0 comments
Closed

Always use .dorpsgek.yml of main (master) branch #7

TrueBrain opened this issue Sep 16, 2019 · 0 comments

Comments

@TrueBrain
Copy link
Member

@TrueBrain TrueBrain commented Sep 16, 2019

Currently when you push to branches, it picks the .dorpsgek.yml from this branch. This is somewhat odd, as that requires branches in the repository to be in sync with the master. Additionally, the .dorpsgek.yml allows to filter which branches report, which is a bit of a contradiction with the current implementation.

The most clean solution is to always use master instead of what-ever branch is used to push to.

LordAro added a commit to LordAro/DorpsGek that referenced this issue Dec 26, 2019
LordAro added a commit to LordAro/DorpsGek that referenced this issue Dec 26, 2019
@LordAro LordAro closed this in #12 Dec 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant
You can’t perform that action at this time.