Anyone have suggestions for getting some tools in place to monitor for when changes happen that match certain criteria (obvious one being when certain files change)? Hosting-wise, we use BitBucket Cloud, though I can’t find anything built-in that’d be useful (seems like most cloud-based solutions don’t offer pre-receive hook customisation?)

We’ve had some “issues” with people not considering the impact of changes to certain code, and just want a little more handholding before the next time that sort of issue happens. I’m sure I could rig something either with a webhookey endpoint, or a CI build that does it, but it just seems like the sort of thing there’d be a pre-built tool for.

Any ideas?

  • SorteKanin@feddit.dk
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    On GitHub i might’ve reached for a codeowners file for the specific files you’re talking about. Then you’d be automatically added to pull request reviews. But not sure if that what you’re asking.

  • muhanga@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    If you are using BitBucket Cloud you can create pr rules to include people into Review based on files change. And then you can create a user for a bot to monitor those PRs using standard BB notification emails. Of course if there is not much PRs bot is Overkill and human will be enough.

    You can always “just” create a static script that pulls repo check diff for files and email people if something is found. This way you don’t link your solution to the git cloud offering.

  • beeng@discuss.tchncs.de
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    You can make a CI run for when certain path filters are hit.

    Make this CI run mandatory to be passing for the merge to pass. You can see when this CI is run that “special people” need to check the PR also

  • yogsototh@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    As you only mention git and not any git hosting. I would say you could easily use git hooks. Fir you and probably ask everyone in your team to install the same git hooks to have a chance to review changes before they are commited.

    For my team there is an init-git-repo.sh shell script in our repository. When you execute it, it will install all the git-hooks fir your local repository.

    You can use them to add checks during commit, merge, etc…

    Edit: I read a bit too fast. As you are using bitbucket there id probably the equivalent of github’s CODEOWNER file as already proposed in another comment.