Replies: 3 comments
-
+1 we have people downstream who depend on database structure and it would be preferable if we could automate keeping them informed (otherwise we have to get each dev to know to go notify this team that they probably don't even know exists, and to remember to do it when it's currently not a part of their workflow). |
Beta Was this translation helpful? Give feedback.
-
It is a feature I will also glad to see. It is very help full when working on repos with heavy traffic. Example for that are deployment repos in many organization in which each directory contains the auto-deployment files for a specific project |
Beta Was this translation helpful? Give feedback.
-
I would instead ask for filtering on workflows by label. then you use some other means to label your PRs based on what they contains. pro-tip: if you think you need to treat prs differently because the contents are in different folders, then you should really be thinking about a monorepo so you can programatically express and explore the dependancy graph of your repos components. trying to globstar folders is just a piss poor alternative. |
Beta Was this translation helpful? Give feedback.
-
I'm attempting to integrate a notification to a channel whenever a pull request is opened for specific folders. It would be most excellent if this was handled out of the box. For example, if a PR was created in a
*/migrations/*
folder, we would get an alert in a database specific channel.Beta Was this translation helpful? Give feedback.
All reactions