Mechanism for skipping arbitrary commits

[tschwinge]

Other than flagging certain commits as suggested in #18 "Check for non-gccrs things in the commits we cherry-pick", does gerris (intend to) have a mechanism for skipping arbitrary commits, for example by path matching (for .github/[...] etc. files), and/or by putting a marker into the Git commit log or similar (for commits that are local-only for other reasons)?

[tschwinge]

Aha, I now found that topic was also briefly discussed in https://gcc-rust.zulipchat.com/#narrow/stream/281658-compiler-development/topic/Gccrs.20Beyond.3A.20Return.20of.20the.20Upstreaming/near/420272660 ff.

[CohenArthur]

I think this should still be something we add - it might be useful to provide a list of commits that we know will cause failures, or should be moved/cherry-picked afterwards. so it makes sense to me