Skip to content
This repository has been archived by the owner on Jun 9, 2021. It is now read-only.

wording of new "trigger conditions" #68

Closed
andreineculau opened this issue Sep 21, 2015 · 3 comments
Closed

wording of new "trigger conditions" #68

andreineculau opened this issue Sep 21, 2015 · 3 comments

Comments

@andreineculau
Copy link

Thanks for fixing #64 ! The wording and the positioning (before Triggers) could be improved a bit though from:

Trigger if pull request
* Has, or has no, merge conflicts
* Has no merge conflicts
* Has merge conflicts

Triggers
...

to:

Triggers
...

Triggers apply
* always
* to PRs with merge conflicts
* to PRs without merge conflicts

and in accordance with #71 , it should actually be

Triggers
...

Triggers do not apply to
[ ] PRs with merge conflicts
[ ] PRs without merge conflicts
[ ] open PRs
[ ] merged PRs
[ ] declined PRs
@tomasbjerre
Copy link
Owner

Changed texts in this issue, continuing discussion in #71

@tomasbjerre
Copy link
Owner

Released in 2.4. So only available for Bitbucket 4.

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

No branches or pull requests

2 participants