Mention community forks for Danger
What does this MR do and why?
The only way to get the fully Danger experience from a fork is by using the community forks... so let's include that info in the docs
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @leetickett-gitlab
changed milestone to %16.7
@gitlab-community/maintainers I would love to hear your thoughts here please
It also reminds me, we should probably revisit the community forks and find some more ways to promote them/make it easier to use them (maybe we automatically grant access when someone has an MR merged for example...)
added docs-only label
- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@leetickett-gitlab - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
- A deleted user
1 Message This MR contains docs in the /development directory. Any Maintainer, other than the author, can merge. You do not need tech writer review. If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Lee Tickett
- Resolved by Lee Tickett
requested review from @sgarg_gitlab
enabled an automatic merge when the pipeline for e1e7341f succeeds
mentioned in commit 2466ebab
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowpost-deploy-db-staging label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label