Skip to content

Add note on the branch naming for documentation changes

What does this MR do?

Clarify documentation changes.

Why was this MR needed?

To educate contributors on the branch naming scheme used.

Are there points in the code the reviewer needs to double check?

Not as far as I know

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

None.


Some notes: I'm now unsure of the usefulness of this contribution, considering the solution is well described in https://docs.gitlab.com/ce/development/documentation/index.html#branch-naming.

I'll leave it up to @tmaczukin to decide on that.

Merge request reports