Update GitLab Features authored by Slominski, Ryan's avatar Slominski, Ryan
...@@ -19,7 +19,7 @@ Items that I wish were available: ...@@ -19,7 +19,7 @@ Items that I wish were available:
- We can't group issues together across projects (via Issue Boards and EPICS) because of Free Tier in fully productive way. - We can't group issues together across projects (via Issue Boards and EPICS) because of Free Tier in fully productive way.
- [No group-level priority labels](https://gitlab.com/gitlab-org/gitlab/-/issues/16920), so we can't prioritize tasks consistently and easily in TODO Lists (otherwise, TODO could have been a work-around for not having Issue Boards...) - [No group-level priority labels](https://gitlab.com/gitlab-org/gitlab/-/issues/16920), so we can't prioritize tasks consistently and easily in TODO Lists (otherwise, TODO could have been a work-around for not having Issue Boards...)
- We can't - We can't
configure an issue template at the group level because of Free Tier: [Group Templates](https://docs.gitlab.com/user/project/description_templates/#set-group-level-description-templates). configure an issue template at the group level because of Free Tier: [Group Description Templates](https://docs.gitlab.com/user/project/description_templates/#set-group-level-description-templates).
- We can't configure a group level CONTRIBUTING.md file, and users are forced to copy and paste every time (have fun making updates too) or otherwise ignore (and there is no way to turn off prompt on right side of every project if your CONTRIBUTING.md file is missing. - We can't configure a group level CONTRIBUTING.md file, and users are forced to copy and paste every time (have fun making updates too) or otherwise ignore (and there is no way to turn off prompt on right side of every project if your CONTRIBUTING.md file is missing.
- We can't disable Evidence Collection on releases. This is a feature that appears to be solving a problem we don't have, at least not yet. GitHub didn't have this, and I don't see any reason for it. It is just distracting and confusing. Apparently if we use a bogus historical release date it might disable it, but using a bogus date isn't great as that's one of the primary pieces of important info on a release. - We can't disable Evidence Collection on releases. This is a feature that appears to be solving a problem we don't have, at least not yet. GitHub didn't have this, and I don't see any reason for it. It is just distracting and confusing. Apparently if we use a bogus historical release date it might disable it, but using a bogus date isn't great as that's one of the primary pieces of important info on a release.
- We can't disable the CHANGELOG.md prompt, meaning if you don't have one, you'll be endlessly prompted to add one. A CHANGELOG is great, but it is really just duplicating the release notes associated with a release. You don't really need both. GitHub doesn't push users to use a CHANGELOG, and historically all changes in my GitHub workflows (the release notes) have just been included in the release itself. - We can't disable the CHANGELOG.md prompt, meaning if you don't have one, you'll be endlessly prompted to add one. A CHANGELOG is great, but it is really just duplicating the release notes associated with a release. You don't really need both. GitHub doesn't push users to use a CHANGELOG, and historically all changes in my GitHub workflows (the release notes) have just been included in the release itself.
... ...
......