Add support for posting notices as GitLab Issues#12
Open
jhuntwork wants to merge 1 commit intojustwatchcom:masterfrom
Open
Add support for posting notices as GitLab Issues#12jhuntwork wants to merge 1 commit intojustwatchcom:masterfrom
jhuntwork wants to merge 1 commit intojustwatchcom:masterfrom
Conversation
Slack is great, but we prefer track events like this as issues to follow up on via a private GitLab server. If the right combination of GITLAB env variables are set, this will create a new issue for each new release. Since this adds a new destination type, and it's uncertain if that is desirable, for now there is bit of code duplication just to demonstrate the feature. Thanks for considering!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Slack is great, but we prefer track events like this as issues to follow up on
via a private GitLab server. If the right combination of GITLAB env
variables are set, this will create a new issue for each new release.
Since this adds a new destination type, and it's uncertain if that is
desirable, for now there is bit of code duplication just to demonstrate
the feature.
Thanks for considering!