Add Github Pull Request Template
Maintainers usually reply within 6 days
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- developer-experience, documentation
Research direction
Review the existing .github/pull_request_template.md files in the SSDT repositories mentioned in the issue, including Labor Status Form and CELTS. Add the corresponding pull request template to BCSR at .github/pull_request_template.md. Done means BCSR pull requests use the shared template for consistent formatting.
Written by the indexing model from the issue text.
Description
Issue Description:
In SSDT's main repos such as Labor Status Form (LSF) and CELTS, there are .github/pull_request_template.md which have a pull request template. This should be implemented in BCSR as well to ensure standard and consistency across pull requests.
- Dominant language
- CSS
- Stars
- 0
- Forks
- 9
- Avg merge
- 9d 22h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BCStudentSoftwareDevTeam/bcsr
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#135 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#132 · 1 comment ·
Maintainers usually reply within 6 days
-
Prefix type enforcementPossibly taken @Ayeyomeday claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
BCStudentSoftwareDevTeam/bcsr#131 · 1 assignee ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BCStudentSoftwareDevTeam/bcsr#130 ·
Maintainers usually reply within 6 days
-
Add CODE_OF_CONDUCT.md for Community ExpectationsPossibly taken @Dumisani-C claimed this 13 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BCStudentSoftwareDevTeam/bcsr#110 · 1 assignee ·
Maintainers usually reply within 6 days
All issues in BCStudentSoftwareDevTeam/bcsr
Similar issues
-
ci hacktoberfest help wanted size/small type/bug type/docs type/enhancement up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Redo-San/RedoSan-Authenticity#527 ·
Maintainers usually reply within 1 day
-
skillfs: one malformed chat-log line aborts the entire skill-usage analysis (skill_usage_from_chat_logs.py)Possibly taken @zjncs claimed this today. Opencomponent:skillfs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
agentic-os-org/ANOLISA#6116 · 1 comment ·
Maintainers usually reply within 1 day
-
kwok: shared-cluster runs leak kube-system releases between recipes, failing inventory read-backOpenarea/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day