Project Options

{% for key in repo.settings | sort %} {% if not g.issues_enabled and not g.issues_project_disabled and key in ['issue_tracker', 'issues_default_to_private'] %} {% elif not config.get('DOC_APP_URL') and key in ['project_documentation'] %} {% elif not config.get('WEBHOOK') and key in ['Web-hooks'] %} {% else %} {% if key in ['Web-hooks'] %}
{% elif key in ['Minimum_score_to_merge_pull-request'] %}
{% elif repo.settings[key] in [True, False, 'y'] %}
{% else %}
{% endif %} {% endif %} {% endfor %}

{{ form.csrf_token }}

{% if config.get('WEBHOOK') and repo.settings['Web-hooks'] %}
{{ form.csrf_token }}
{% endif %}

Learn more about

Pagure offers the possibility to flag pull-requests and commits. A flag is a way for a third-party tool to provide feedback on a pull-request or a commit.
Two settings above allow notifying contributors and watchers of a project when new flags are being added.
The flags documentation.

Pagure supports leaving the issue tracker activated but making it read-only, thus letting people access to the existing tickets without allowing creating new tickets or comments.

Pagure supports blocking direct commit access to a project and enforcing all changes to a project to be done via pull-requests.

Pagure supports making the roadmap page the front page of the issue list.

Lets pagure send fedmsg notification for all actions performed in a project (new ticket, new pull-request, new comment...).
Sending fedmsg notifications upon commits is performed via a git hook though, see the Hooks section in this settings page.