Text Blame Raw
Usage
=====

Using pagure should come fairly easily, especially to people already used
to forges such as GitHub or GitLab. There are however some tips and tricks
which can be useful to know and that this section of the doc covers.


One of the major difference with GitHub and GitLab is that for each project
on pagure, four git repositories are made available:

* A git repository containing the source code, displayed in the main section
  of the pagure project.
* A git repository for the documentation
* A git repository for the issues and their metadata
* A git repository for the metadata for pull-requests


Issues and pull-requests repositories are not public and only available to
admins and committers of the project, since they can contain private tickets.

You can find the URLs to access or clone these git repositories on the
overview page of the project. On the menu on the right side, there is a menu
`Source GIT URLs`, next to it is a little `more` button, by clicking on it
as project admin or committer you will be given the URLs to the other three git repos.

Each section correspond to one of the four git repositories created for each
project.



Contents:

.. toctree::
   :maxdepth: 2

   first_steps
   forks
   read_only
   pull_requests
   markdown
   project_settings
   project_acls
   roadmap
   flags
   using_doc
   using_webhooks
   ticket_templates
   pr_custom_page
   theming
   upgrade_db
   pagure_ci
   quick_replies
   troubleshooting
   tips_tricks


Pagure API
----------

The API documentation can be found at `https://pagure.io/api/0/ <https://pagure.io/api/0/>`_
or in ``/api/0/`` of you local pagure instance.