Detection of /doc-only changes in non-docs branch, and vice versa
-
What happens when someone commits a non-
/doc
code change to a docs branch? Is there something in the current default CE or EE pipeline that fails? Is it clear why it fails? -
When someone commits a
/doc
-only change but fails to use a docs branch, should we have DangerBot remind them? Something like this:For future reference, when only making changes to the /doc path, using the special docs branch names will skip the unnecessary pipeline steps required for other code. However, you can still merge this branch if the current (extended) pipeline passes.