---
name: Bug #Used as UI element for the button on the New Issues page
about: Use this template to submit a new bug #Used as description text on the New Issues page
title: [BUG]: <Describe issue> #Used as placeholder name for newly created issue
---
# Description
# Expected result
# Actual result
# Steps to reproduce
1.
2.
# Environment
-OS:
-Software version:
-Screenshots:
---
title: "[PR]: <Insert title>"
---
<!-- Thank you for your contribution! -->
<!-- Include if applicable: -->
Fixes: #nnn <!-- tracking issues that this PR will close -->
**Related**: _Relevant tracking issues, for context_
**Merge before/after**: _Dependent or prerequisite PRs_
**Description**
<!-- Describe your changes here. The more detail, the easier the review! -->
**User facing changes (remove if N/A)**
<!-- Describe any user facing changes this PR introduces. -->
<!-- "Before" and "After" sections work great - bonus points for screenshots! -->
<!-- Be sure all docs have been updated as well! -->
**Follow-up Work (remove if N/A)**
<!-- Mention any related follow up work to this PR. -->
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Create issue and pull request templates\n\nThis page describes how to create and configure issues templates and pull request templates for Secure Source Manager.\n\n\u003cbr /\u003e\n\nRequired roles\n--------------\n\n\nTo get the permissions that\nyou need to work with issues and pull request templates,\n\nask your administrator to grant you the\nfollowing IAM roles:\n\n- [Secure Source Manager Instance Accessor](/iam/docs/roles-permissions/securesourcemanager#securesourcemanager.instanceAccessor) (`roles/securesourcemanager.instanceAccessor`) on the Secure Source Manager instance\n- [Secure Source Manager Repo Writer](/iam/docs/roles-permissions/securesourcemanager#securesourcemanager.repoWriter) (`roles/securesourcemanager.repoWriter`) on the repository\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nYou might also be able to get\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\nFor information on granting Secure Source Manager roles,\nsee [Access control with IAM](/secure-source-manager/docs/access-control) and\n[Grant users instance access](/secure-source-manager/docs/grant-users-instance-access).\n\nTemplates overview\n------------------\n\nIssues and pull request templates let you standardize the\ninformation contributors provide to a repository. Issue templates offer\npredefined options a user can choose from depending on the type of issue they\nare submitting and the template types available. A pull request template is\nautomatically applied to all pull requests, ensuring consistent contributions to\nthe repository.\n\nTemplates can be created by anyone with permission to merge files in a\nrepository.\n\nCreate an issues template\n-------------------------\n\nSecure Source Manager lets you define issues templates using Markdown files in multiple\nlocations in your repository. You can create multiple issue templates for\ndifferent purposes. For example, you may want to have a separate templates for\nreporting bugs and submitting feature requests.\n\n1. Create a template that begins with the following information, in this exact\n format:\n\n ---\n name: TEMPLATE_NAME\n about: Insert description of template\n title: Placeholder title for the new issue when it is created\n ---\n\n2. Provide a name, and description. These are required and are used in the UI\n of the New Issues page.\n\n3. You can optionally include a title that is used as a placeholder title when a\n new issue is created.\n\n4. Below the required material, include any information you would like to\n be visible in the issue description that will assist users in providing\n necessary information.\n\n5. Save your template as a Markdown file in one of the following locations:\n\n - `/.securesourcemanager/ISSUE_TEMPLATES/`\n - `/.securesourcemanager/issue_templates/`\n\n| **Note:** If templates are found in more than one location, Secure Source Manager uses the template from the first folder in your directory.\n\n### Default issues template\n\nSecure Source Manager also supports the definition of a single default template. This\ntemplate should be defined in one of the following locations:\n\n- `/.securesourcemanager/ISSUE_TEMPLATE.md`\n- `/.securesourcemanager/issue_template.md`\n\nWhen a user creates a new issue, Secure Source Manager prompts that user to select a\ntemplate, if any are available, or selects the default template. If there's no\ndesignated default template, nothing is pre populated into the new issue.\n\n### Example Issues template\n\nThe first 5 lines of the template must follow the conventions outlined in the\nfollowing example. Any additional information can be formatted in Markdown to\nsuit the needs of the issue type. \n\n ---\n name: Bug #Used as UI element for the button on the New Issues page\n about: Use this template to submit a new bug #Used as description text on the New Issues page\n title: [BUG]: \u003cDescribe issue\u003e #Used as placeholder name for newly created issue\n ---\n # Description\n\n # Expected result\n\n # Actual result\n\n # Steps to reproduce\n 1.\n 2.\n\n # Environment\n -OS:\n -Software version:\n -Screenshots:\n\nCreate a pull request template\n------------------------------\n\n1. Create a template that begins with the following information, in this exact\n format:\n\n ---\n title: \"[PR]: \u003cInsert title\u003e\"\n ---\n\n2. Below the required material, include any information you would like to\n be visible in the issue description to assist users in providing\n necessary information. See the example template in the following section for\n more details.\n\n3. Save the template as a Markdown file in one of the following locations inside\n a repository:\n\n - `/.securesourcemanager/PULL_REQUEST_TEMPLATE.md`\n - `/.securesourcemanager/pull_request_template.md`\n\nWhen you create a new pull request, Secure Source Manager checks if a template exists in\nany of the defined locations and loads it. If you included **title** information\nin your template, it's automatically populated in the new pull request to\nprovide users with a defined format to follow. Any additional information you\nincluded is added to the pull request description to be updated by the\nsubmitting user.\n\n### Example Pull Request template\n\nThe first 3 lines of the template must follow the conventions shown in the\nfollowing example. Everything that follows is options and should assist your\nusers in creating pull requests that follow your conventions. \n\n ---\n title: \"[PR]: \u003cInsert title\u003e\"\n ---\n \u003c!-- Thank you for your contribution! --\u003e\n\n \u003c!-- Include if applicable: --\u003e\n Fixes: #nnn \u003c!-- tracking issues that this PR will close --\u003e\n **Related**: _Relevant tracking issues, for context_\n **Merge before/after**: _Dependent or prerequisite PRs_\n\n **Description**\n \u003c!-- Describe your changes here. The more detail, the easier the review! --\u003e\n\n **User facing changes (remove if N/A)**\n \u003c!-- Describe any user facing changes this PR introduces. --\u003e\n \u003c!-- \"Before\" and \"After\" sections work great - bonus points for screenshots! --\u003e\n \u003c!-- Be sure all docs have been updated as well! --\u003e\n\n **Follow-up Work (remove if N/A)**\n \u003c!-- Mention any related follow up work to this PR. --\u003e\n\nWhat's next\n-----------\n\n- Visit [Work with issues and pull requests](/secure-source-manager/docs/work-with-issues-pull-requests) for details on how to work with issues and pull requests in Secure Source Manager."]]
