this post was submitted on 25 Jul 2023
12 points (92.9% liked)

Programming

17001 readers
330 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
12
[help] Tools for monitoring changes in a Git repo (lemmy.tr00st.co.uk)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
5 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 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