- Correctly align edit button for groups in repo settings (Ryan Lerch)

  - Fix all-around sidebar heading borders (Ryan Lerch)

  - Remove incorrect count label on related PRs (Ryan Lerch)

  - Add reporter and assignee to notification emails headers (Lenka Segura)

  - Make sure that ticket changes don't get duplicated (Patrick Uiterwijk)

  - Fix the git ssh urls in the templates

  - Include the targeted branch in the list of PRs

  - Separately link user/namespace/name

  - Fix the pagination when listing projects via the view_projects endpoints

  3.6 (2017-08-14)

  - When creating the pull-request, save the commit_start and commit_stop

  - Ensure there is a date before trying to humanize it

  - Fixing showing tags even when some of them are not formatted as expected

  - Add merge status column in pull requests page (Abhijeet Kasurde)

  - Allow user with ticket access to edit custom fields, metadata and the privacy

    flag (Vivek Anand)

    (Eashan)

  - Document how to filter out for issues having a certain tag in the tips and

    tricks section

    the configuration

  - Add support for admin API token to pagure-admin

  - Make clicking on 'Unassigned' filter the unassigned PR as it does for issues

  - Add a configuration key allowing to hide some projects that users have access

    to only via these groups

  - Fix figuring out which branches are not merged in namespaced project

    or more

  - Allow dropping all the priorities info of an issue

  - Do not edit multiple times the milestone info when updating a ticket

  - Make interacting with the different git repos a locked process to avoid

    lost/orphan commits

  - Update API doc for api_view_user (Clement Verna)

  - Do not automatically update the last_updated or updated_on fields

  - Make alembic use the DB url specified in the configuration file of pagure

  - Only connect to the smtp server if we're going to send an email

  - Let the notifications render correctly when added by the SSE server

  - Fix the URL for pull request on the list of branches of a fork (Rahul Bajaj)

  - Adjust the markdown processor to have 1 regex for all cross-project links

  - Hide the title of private tickets when linking to them in markdown

  - Show user activity in pagure on the user's page

  - Add the possibility to subscribe to issues

  - Don't track pagure_env (venv) dir (Paul W. Frields)

  - Setting Mail-Followup-To when sending message to users (Sergio Durigan Junior)

    (Fixed by Ryan Lerch and I)

    commit (Clement Verna)

  - Fix behavior of view of tree if default branch is not 'master' (Vivek Anand)

  - Fix checking the release folder for forks

  2.2.1 (2016-06-01)

  ------------------

  - Fix diffs not showing for additions/deletions for files under 1000 lines (Ryan

    Lerch)

  - Split out the commits page to a template of its own (Ryan Lerch)

  - Fix the fact that the no readme box show on empty repo (Ryan Lerch)

  - Fix the of the Docs tab and the Fork button with rounded corners (Pedro Lima)

  - Expand the information in the notifications message when a PR is updated (Ryan

    Lerch)

  - Improve the description of the git hooks (Lubomír Sedlář)

  - Allow reply to a notification of pagure and setting the reply email address as

    Cc

  FAST_CELERY_QUEUE

  ~~~~~~~~~~~~~~~~~

  are triggered by the web frontend and need to be processed quickly for the

  best user experience.

  MEDIUM_CELERY_QUEUE

  ~~~~~~~~~~~~~~~~~~~

  are triggered by the web frontend and need to be processed but aren't critical

  for the best user experience.

  SLOW_CELERY_QUEUE

  ~~~~~~~~~~~~~~~~~

  are triggered by the web frontend, are slow and do not impact the user

  experience in the user interface.

  STOMP_NOTIFICATIONS

  ~~~~~~~~~~~~~~~~~~~

  `stomp protocol <https://stomp.github.io/>`_. All other stomp-related

  settings don't need to be present if this is set to ``False``.

  ALWAYS_STOMP_ON_COMMITS

  ~~~~~~~~~~~~~~~~~~~~~~~

  notifications on commits made on all projects in a pagure instance.

  Defaults to: ``False``.

  ~~~~

  This configuration key lists all the ACLs that can be associated with an API

  This key it not really meant to be changed unless you really know what you

  are doing.

  USER_ACLS

  ~~~~~~~~~

  can be associated with an API token of a project in the (web) user interface.

  Use this configuration key in combination with ``ADMIN_API_ACLS`` to disable

  ADMIN_API_ACLS

  ~~~~~~~~~~~~~~

  can be generated by the ``pagure-admin`` CLI tool by admins.

  Defaults to: ``['issue_comment', 'issue_create', 'issue_change_status', 'pull_request_flag', 'pull_request_comment', 'pull_request_merge', 'generate_acls_project', 'commit_flag', 'create_branch']``

  CROSS_PROJECT_ACLS

  ~~~~~~~~~~~~~~~~~~

  can be associated with a project-less API token in the (web) user interface.

  These project-less API tokens can be generated in the user's settings page

  and allows action in multiple projects instead of being restricted to a

  ENABLE_TICKETS_NAMESPACE

  ~~~~~~~~~~~~~~~~~~~~~~~~

  system is enabled.

  So if your pagure instance has ``ENABLE_TICKETS`` as ``True`` and sets

  ``ENABLE_TICKETS_NAMESPACE`` to ``['tests', 'infra']`` only the projects opened

  FEDMSG_NOTIFICATIONS

  ~~~~~~~~~~~~~~~~~~~~

  <http://www.fedmsg.com/>`_.

  Defaults to: ``False``.

  FEDORA_MESSAGING_NOTIFICATIONS

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  `fedora-messaging <>`_.

  Defaults to: ``False``.

  ALWAYS_FEDMSG_ON_COMMITS

  ~~~~~~~~~~~~~~~~~~~~~~~~

  notifications on commits made on all projects in a pagure instance.

  Defaults to: ``True``.

  LOCAL_SSH_KEY

  ~~~~~~~~~~~~~

  or have a third party tool do it for you.

  In most cases, it will be fine to let pagure handle it.

  DEPLOY_KEY

  ~~~~~~~~~~

  entire pagure instance. This feature enable to add extra public ssh keys

  that a third party could use to push to a project.

  USER_NAMESPACE

  ~~~~~~~~~~~~~~

  the user's username, behaving in this way in a similar fashion as github.com

  or gitlab.com.

  A run of pagure-ci can be manually triggered if some key sentences are added

  as comment to a pull-request, either manually or via the "Rerun CI" dropdown.

  unexpected issues unrelated to the test suite.

  to trigger this pagure-ci run. The format is following: ``{"<sentence>":

  {"name": "<name of the CI>", "description": "<short description>"}}``

  REQUIRED_GROUPS

  ~~~~~~~~~~~~~~~

  added to a project with commit or admin access.

  Defaults to: ``{}``

  CASE_SENSITIVE

  ~~~~~~~~~~~~~~

  instead of its default: case-insensitive.

  Defaults to: ``False``

  PROJECT_NAME_REGEX

  ~~~~~~~~~~~~~~~~~~

  validate new project name.

  Defaults to: ``^[a-zA-z0-9_][a-zA-Z0-9-_]*$``

  ALLOWED_PREFIX

  ~~~~~~~~~~~~~~

  will not require creating a group for users to create projects in.

  Defaults to: ``[]``

  BLACKLISTED_GROUPS

  ~~~~~~~~~~~~~~~~~~

  Defaults to: ``['forks', 'group']``

  ENABLE_GROUP_MNGT

  ~~~~~~~~~~~~~~~~~

  group, adding or removing users in that group) groups in this pagure instance.

  If turned off, groups and group members are to be managed outside of pagure

  and synced upon login.

  ENABLE_USER_MNGT

  ~~~~~~~~~~~~~~~~

  removing them from a project) in this pagure instance.

  If turned off, users are managed outside of pagure.

  SESSION_COOKIE_NAME

  ~~~~~~~~~~~~~~~~~~~

  by pagure.

  Defaults to: ``'pagure'``

  SHOW_PROJECTS_INDEX

  ~~~~~~~~~~~~~~~~~~~

  logged in users.

  Defaults to: ``['repos', 'myrepos', 'myforks']``

  commit is made.

  However some pagure instances may be using a different notification mechanism on

  commits and thus may not want this feature to double the notifications received.

  watching commits on a project upon commits.

  Defaults to: ``True``

  SYNTAX_ALIAS_OVERRIDES

  ~~~~~~~~~~~~~~~~~~~~~~

  on certain files based on their extensions.

  It should be a dictionary containing the file extensions as keys and

  Pagure can be integrated with `repoSpanner <https://repospanner.org>`_

  allowing to deploy pagure in a load-balanced environment since the git

  Support for this integration has been included in Pagure version 5.0 and higher.

  REPOSPANNER_REGIONS

  ~~~~~~~~~~~~~~~~~~~

  is deployed and thus with which this pagure instance can be integrated.

  An example entry could look like:

  MQTT_TOPIC_PREFIX

  ~~~~~~~~~~~~~~~~~

  This prefix will be added to the topic used by pagure thus allowing the mqtt

  admins to specify a parent topic for all pagure-related messages.

  ALWAYS_MQTT_ON_COMMITS

  ~~~~~~~~~~~~~~~~~~~~~~

  notifications on commits made on all projects in a pagure instance.

  Defaults to: ``False``.

  FILE_SIZE_HIGHLIGHT

  ~~~~~~~~~~~~~~~~~~~

  or diff should have to have syntax highlighting. Everything above this limit

  will not have syntax highlighting as this is a memory intensive procedure that

  easily leads to out of memory error on large files or diff.

  BOOTSTRAP_URLS_CSS

  ~~~~~~~~~~~~~~~~~~

  CSS file since the files hosted on apps.fedoraproject.org used in pagure.io

  are not restricted in browser access.

  BOOTSTRAP_URLS_JS

  ~~~~~~~~~~~~~~~~~

  JS file since the files hosted on apps.fedoraproject.org used in pagure.io

  are not restricted in browser access.

      (for ``failure`` vs ``error`` think of the test system ran the tests but

      they failed vs the test system did not get to run the tests)

    details about the outcome of the task. For example this could be used for

    test coverage, or the number of test that failed/passed.

  The principal is:

  * pagure will trigger a build on jenkins when a pull-request is created,

    is pushed (if pagure-ci is configured to trigger on commit).

  * pagure will send a few information to jenkins when triggering a build:

  --------------------------------------------

  Very much in the same way pagure allows you to filter for issues having a

  To do this, simply prepend a ``!`` in front of the tag.

  Example:

  Basically, pagure will make a HTTP POST request to one or more third party

  server/application with information about what is or just happened.

  --------------------------------

  To set-up a web-hook, simply go to the settings page of your project and