{% extends "coprs/detail/settings.html" %} {% from "_helpers.html" import render_field, render_form_errors, copr_url %} {% set selected_monitor_tab = "integrations" %} {%block settings_breadcrumb %}Integrations{% endblock %} {% block tab_content %}
Set up an integration with a Git hosting website and get Copr build statuses reported in pull requests and commits.
Copr will now rebuild the package every time it receives an update event - usually for every new commit, every new tag, or every opened pull request.
If valid credentials for a source repository are entered below, Copr will report back build results for a particular pull request or commit. Only one source repository at time can be set for pull request and commit flagging.
Don’t get confused by “Activate fedmsg notifications” in the “Project options” section: That’s only for Pagure UI-related actions. Scroll down until you reach the “Hooks” section.
To enable commit and pull request flagging, enter a Pagure public clone repo URL and an associated API key below. To create a new key, go to your Pagure project settings and find section "API keys".
{{ render_form_errors(pagure_form) }}Settings / Webhooks. Add webhook button. Payload URL field with the url above. application/json as the content type. Add webhook button. Settings / Webhooks. URL field with the url above. Push events and Tag push events as event triggers. Add webhook button. Settings / Workflow / integrations / Add webhook. URL field with the url above. Repository Push. Save button. Use the GitLab/GitHub/Bitbucket steps above (when needed), or simply