index.rst 2.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. Usage
  2. =====
  3. Using pagure should come fairly easily, especially to people already used
  4. to forges such as GitHub or GitLab. There are however some tips and tricks
  5. which can be useful to know and that this section of the doc covers.
  6. One of the major difference with GitHub and GitLab is that for each project
  7. on pagure, four git repositories are made available:
  8. * A git repository containing the source code, displayed in the main section
  9. of the pagure project.
  10. * A git repository for the documentation
  11. * A git repository for the issues and their metadata
  12. * A git repository for the metadata for pull-requests
  13. Issues and pull-requests repositories contain the meta-data (comments,
  14. notifications, assignee...) from the issues and pull-request. They are are
  15. not public and only available to admins and committers of the project,
  16. since they may contain private information.
  17. You can use these repositories for offline access to your tickets or
  18. pull-requests (the `pag-off <https://pagure.io/pag-off>`_ project for example
  19. relies on a local copy of the issue git repository). They are designed to
  20. allow you to have full access to all the data about your project.
  21. One of the original idea was also to allow syncing a project between multiple
  22. pagure instances by syncing these git repositories between the instances.
  23. You can find the URLs to access or clone these git repositories on the
  24. overview page of the project. On the top right of the page, in the drop-down
  25. menu entitled ``Clone``. Beware that if documentation, the issue tracker or
  26. the pull-requests are disabled on the project, the corresponding URL will
  27. not be shown.
  28. Contents:
  29. .. toctree::
  30. :maxdepth: 2
  31. first_steps
  32. forks
  33. read_only
  34. http_push
  35. pull_requests
  36. markdown
  37. project_settings
  38. project_acls
  39. roadmap
  40. flags
  41. magic_words
  42. using_doc
  43. using_webhooks
  44. ticket_templates
  45. pr_custom_page
  46. theming
  47. upgrade_db
  48. pagure_ci
  49. quick_replies
  50. troubleshooting
  51. tips_tricks
  52. Pagure API
  53. ----------
  54. The API documentation can be found at `https://pagure.io/api/0/ <https://pagure.io/api/0/>`_
  55. or in ``/api/0/`` of you local pagure instance.