doc: Shipwright Webhook Feed #261
Open
Conversation
This file contains 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
This community README update serves as an announcement that any community member can receive automated notifications of Shipwright activity through GitHub's webhook feed mechanism. For now, anyone can request access by emailing the project admins ([email protected]). Maintainers with org-wide write permission will then need to work with the requestor to obtain the desired endpoint, webhook secret, payload format, and types of events to receive. In the future, we can gather some of this information up front through a GitHub issue template (obviously not the secret - that should be exchanged through a proper private channel). This was prompted by previous work I did to send GitHub issue and PR events to Fedora's GitHub2FedMsg bus [1]. I had set this up on behalf of Red Hat to sync data from GitHub to Red Hat's issue tracker. There is no compelling reason to restrict this sort of feed to just Red Hat; any community member who wants to track our project work in their own systems should be able to do so. [1] https://github.com/fedora-infra/github2fedmsg Signed-off-by: Adam Kaplan <[email protected]>
pull-request-size
bot
added
the
size/XS
openshift-ci
bot
added
the
kind/documentation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
This community README update serves as an announcement that any community member can receive automated notifications of Shipwright activity through GitHub's webhook feed mechanism. For now, anyone can request access by emailing the project admins
([email protected]). Maintainers with org-wide write permission will then need to work with the requestor to obtain the desired endpoint, webhook secret, payload format, and types of events to receive. In the future, we can gather some of this information up front through a GitHub issue template (obviously not the secret - that should be exchanged through a proper private channel).
This was prompted by previous work I did to send GitHub issue and PR events to Fedora's GitHub2FedMsg bus [1]. I had set this up on behalf of Red Hat to sync data from GitHub to Red Hat's issue tracker. There is no compelling reason to restrict this sort of feed to just Red Hat; any community member who wants to track our project work in their own systems should be able to do so.
[1] https://github.com/fedora-infra/github2fedmsg
/kind documentation
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes