Merge branch 'default_gl_templates' into 'develop'

Draft: Add default Gitlab templates for Issues and MR's

See merge request pleroma/pleroma!3714
This commit is contained in:
Ilja 2024-04-19 22:08:44 +00:00
commit ad632d39e5
2 changed files with 24 additions and 3 deletions

View file

@ -2,8 +2,8 @@
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it (e.g. give a thumbs up or leave a comment).
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
@ -15,4 +15,12 @@
* PostgreSQL version (`psql -V`):
### Bug description
### Description
<!--
Please try to be clear what the problem is.
* For bugs it's best to add steps to reproduce, current result and what you expect. Logfiles, screenshots and additional information can also help us better understand the problem.
* For enhancements, make it clear what you expect and what problem you try to solve.
Feel free to link to relevant other issues or merge requests.
-->

View file

@ -0,0 +1,13 @@
<!--
If this PR closes an issue, you can use the "Closes" keyword: Closes <link-to-issue>
If you're still working on the PR, please prepend the title with "DRAFT:"
Provide a proper description so it's clear what you try to do and/or what problem you try to solve.
When an MR is ready for review, feel free to ping the maintainers on the chat so they know your code is ready for review. If you haven't gotten any feedback after a couple of weeks, feel free to ping again.
Please try to resolve issues people bring up in the comments and add proper tests. The latter helps us to be more confident in the code in case we do bigger changes. It also works as a way to document code to other devs working on it. Whatever is tested is expected behaviour, all the rest may very well be a coincidence.
When a new feature is added that also needs changes in the fe, please make an issue or MR for it in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new).
-->