Gazler

It is common in many flows to expect people to do a force push if something is wrong with their pull request, e.g. having 15 commits that look like:

    Try stuff
    Another prototype
    Fix something
    ...
    Revert prototype

It is fairly common (in my experience) for the contributor to be asked to squash those commits.

In my opinion, the more guards in place the better.

I think doing it like that is a neat idea. Perhaps there could be an "advanced" page which is as you describe and the current method could be the "simple" version?

Thanks for the ideas.

I think there are several avenues that could be explored with this. I wanted to stay away from explicitly checking the code initially, as there are other tools aimed at that specific task, however there is no reason something like this couldn't be added into GitCop at a later date.

I had the idea of checking that the user exists in a list of users by specifying a JSON list of users. This means that it could be used to check if a CLA has been signed, but there are other applications too. Does this seem like a reasonable way to do it?

I like the idea of ensuring a test has been added, not sure how to tackle it, but it is certainly worth keeping in mind.

Glad it made sense!

So the match is exact between the non %{..} characters. The idea for scope is the context of the commit, in my libraries I use the name of the class as the scope.

For example with the default format string:

    test string: "fix(User): ensure email address is required"
    format:      "%{type}(%{scope}): %{description}"
    [type: "fix", scope: "User", description: "ensure email address is required"]

So any literal characters are matched exactly and anything inside the capturing %{...} is assigned to that variable.

This does fall over in the following case:

    "fix():(User): ensure email address is required"
    "%{type}(%{scope}): %{description}"
    [type: "fix", scope: "):(User", description: "ensure email address is required"]

It is certainly a candidate for improvement in the future.

This is a great idea, definitely something worth implementing. Thanks for the feedback.

Thanks for the feedback, I hope your dev team find it as valuable as you do.

I'm not too familiar with Atlassian Stash, I will have a search around and see how plausible it would be to integrate.