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

No Config file found #757

Open
raghunandannm opened this issue Jun 18, 2024 · 1 comment
Open

No Config file found #757

raghunandannm opened this issue Jun 18, 2024 · 1 comment

Comments

@raghunandannm
Copy link

We are planning to integrate mergeable in our github repo. As part of this we have created a .github/mergeable.yml file in a feature branch and the mergeable has got triggered as exepcted.

Later on, when we tried to create a new branch from this feature branch the mergeable is not getting triggered and showing up "No Config file found" error. Now, when we touch this mergeable.yml file in this feature branch, then mergeable is getting triggered.

Is there any reason for this? Should mergeable.yml file be available on main/develop branch to get triggered automatically? Or should we have to touch this mergeable.yml file in every PR?

@andekande
Copy link
Contributor

andekande commented Jun 20, 2024

It is intended to have only one mergeable.yaml in the main branch.
If you have conventions for naming additional branches, like 'fix-the-unknown' then you can formulate a rule that only triggers for a specific prefix of a branch, like:

validate:
  - do: baseRef
    must_include:
       regex: '^fix-'
  - do: description
        no_empty:
          enabled: true
          message: Description is required for Fixes 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants