## Summary Release notes starting with `+` doesn't work because RELEASE_NOTE_UPDATE_ACCESS_TOKEN bot will update that to the MR number. ### Detailed Description In the documentation I read: ``` If you just correct a typo or something which really no user cares, name your file +.misc.<random>, this will not provide an entry in the release notes (and no link to a MR) ``` So I tried to create release note `docs/_releasenotes/+.misc.migratingtypo` but bot converted that to the `docs/_releasenotes/3387.misc.migratingtypo`. See !3387. #### Steps to reproduce the issue Create MR with `+.misc.<random>` release note file. #### Result RELEASE_NOTE_UPDATE_ACCESS_TOKEN bot changed it to the `MRnumber.misc.<random>` #### Expected Result RELEASE_NOTE_UPDATE_ACCESS_TOKEN bot will not touch it #### Additional Information <!-- Configuration, data, software versions etc. which are involved. If possible, provide the git commit ID you are running off. --> ## Resolution <!-- OPTIONAL section in case you have concrete ideas for a fix. If unused, delete this entire section --> ### Proposal To be discussed. <!-- Alternatively, you can add a full text or bullet-pointed proposal here for discussion --> ### Specification The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this issue are to be interpreted *in the spirit of* [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119), even though we're not technically doing protocol design. <!-- Bullet-point list of MUST, SHOULD, MAY, SHOULD NOT and MUST NOT. will be added as a result of the proposal discussion process. -->