2 ms·
The big one that I can think of is triggering our "packaging" pipelines. We have some packages published separately from our main releases (which are not publis
by ollien 4y ago
The big one that I can think of is triggering our "packaging" pipelines. We have some packages published separately from our main releases (which are not published via CI), so we have to trigger separate pipelines for them. We could _probably_ have some kind of filter based on directories, and honestly I'm not sure why we don't (probably so it's deliberate).
Anyway, hope that answers your question :)
- mhitza 4y agoMaybe the gh command line can be useful for your use-case. Although you might want to keep the comment trigger style for historical/audit reasons, or if non-devs are allowed to trigger those downstream jobs as well.