Skip to content

Conversation

@jhuntwork
Copy link

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!

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!
Copy link

@dominikschulz dominikschulz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@ramilexe ramilexe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants