hey @iancrowther it seems i don't have permission to view your yml, i keep getting 404. but here is an example i created just for you https://github.com/shine2lay/MergeableTest/runs/520311716
Hi! I want to run validation on pull request, but only if not created by CI users. I want to use the
or validator (which is not mentionned in the docs). I don't know how to write it
version: 2 mergeable: - when: pull_request.* validate: - do: title must_include: regex: "RM2-\\d+]$" - do: label must_include: regex: "^Tag:" fail: - do: checks status: "failure"
version: 2 mergeable: - when: pull_request.opened name: "Greet a contributor" validate:  pass: - do: comment payload: body: > Thanks for creating a pull request! A maintainer will review your changes shortly. Please don't be discouraged if it takes a while.
commentas the action, if you wish checks to be created, you'll have to include
checkaction as well https://mergeable.readthedocs.io/en/latest/actions/check.html
mergable.ymlfile ? I've defined the rules in base branch or organization but it can be overriden by PR and its a security issue. Let's say I've defined
no empty descriptionand someone can override this
ORoperator. Not an ideal solution but doable if the list of reviewers is a finite number that is small enough. Might be useful to create an issue for this to be in the backlog. We can apply a generic implementation for passing regex captures from validators to actions. — Would be great if you can share an example of your use case though. Curious: if you have to speficy a user in the title/desc why not use the ui to request review?
@elieweintraub got it. If you create a gh issue we can queue this into our backlog.
Created mergeability/mergeable#473 for this
ERROR (HttpError): If you would like to help us test the Checks API during its preview period, you must specify a custom media type in the 'Accept' header. Please see the docs for full details. HttpError: If you would like to help us test the Checks API during its preview period, you must specify a custom media type in the 'Accept' header. Please see the docs for full details. at /app/node_modules/@octokit/request/dist-node/index.js:66:23 at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async sendRequestWithRetries (/app/node_modules/@octokit/auth-app/dist-node/index.js:445:12) at async Job.doExecute (/app/node_modules/bottleneck/light.js:405:18)
milestonesetting/filter does solve a different process problem but we may be able to make that work. In a different case, wondering if we are able to fork it and add a scheduling feature and/or a boolean switch? I mean technically we could do that but not sure about licensing or if you would be OK with that. Would the Mergeable team be interested in a PR to add those features?
must_excludecan fix this issue.
Hiya... I'm trying to set up the org-wide defaults like it's defined here ...
So, i've got a
.github repo in the org, it has a
.github/mergeable.yml defined, yet the repo that has the app enabled continuously claims that there's
No Config file found. Any hints?