##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
api: comment_pull_request, added commit_id parameter to validate status changed on particular commit....
api: comment_pull_request, added commit_id parameter to validate status changed on particular commit. - when using the API and creating a comment with status change it's now possible to pass in commit_id, this will allow validation if status change of pull_request is allowed based on the given commit_id. This solves the case when long running test sends approval of pull request which was already updated several times. The commit_id will now validate for which state the approval was made, and prevent accidental aproval of outdated pull requests.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r1269:26e59d48 default
Show More
gist-editing.rst
33 lines | 1.3 KiB | text/x-rst | RstLexer
/ docs / usage / gist-editing.rst
History | Annotation | Raw |Copy content |Copy permalink

Gist Editing

Gists are standalone files that only the creator can edit. To work with gists, click on the :guilabel:`Gists` tab on the |RCM| header. The gist editor also has syntax highlighting.

You can set the following properties for each gist:

  • :guilabel:`Public`: Public gists are as the name suggests, and will show up in searches.
  • :guilabel:`Gist Lifetime`: You can set a gist to expire after a set period by using the :guilabel:`Gist Lifetime` dropdown menu. This means that when the gist expires it will be deleted from the |RCM| gist database.
  • :guilabel:`Private`: This means that the gist will not show up in searches.
  • :guilabel:`Gist access level`: If you create a private gist you can have two levels of privacy with the gist link.
    • :guilabel:`Requires registered account`: This option requires users to have a registered account on the |RCE| instance, otherwise they will not have access to the gist.
    • :guilabel:`Can be accessed by anonymous users`: This option hides the link so that it does not show up in searches, but you can still share it with people outside of your organisation.

For more advanced use of gists, see the gist API options in the :ref:`api`

Gist Management