github/social-tw-website
1
1
Fork 0
mirror of https://github.com/social-tw/social-tw-website.git synced 2026-01-08 23:18:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

fix: linter

Browse Source
This commit is contained in:
ryanycw
2023-09-15 19:31:53 +08:00
parent 22b8b63d57
commit fa7719db51
2 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@@ -1,4 +1,4 @@
Please follow the guidelines in [Contribution.md](https://github.com/social-tw/social-tw-website/blob/main/CONTRIBUTING.md) first, then start to create your pull request here.
Please follow the guidelines in [Contribution.md](https://github.com/social-tw/social-tw-website/blob/main/CONTRIBUTING.md) first, then start to create your pull request here.
## Summary

21
CONTRIBUTING.md
View File

@@ -1,14 +1,17 @@
# Welcome to Unirep Social TW contributing guideline 👋🏻
Thank you for investing your time in contributing to our project!
Thank you for investing your time in contributing to our project!
This guide will give you an overview of the contribution workflow, from opening an issue, creating a PR, reviewing, and merging the PR.
## How do we start the development?
1. Create the branch under social-tw, and name it with the convention of "purpose-scope-unit" (E.g. feat-login-backend)
[Reference to more prefix of the branch](https://wadehuanglearning.blogspot.com/2019/05/commit-commit-commit-why-what-commit.html)
2. Create a pull request and name it with the status and the same name as the branch. E.g. [WIP] feat-post-smart-contract
3. Once the development is done, you can ask for a review. The PR can be merged after approval by **at least one other team member**.
## How do we start the development?
1. Create the branch under social-tw, and name it with the convention of "purpose-scope-unit" (E.g. feat-login-backend)
[Reference to more prefix of the branch](https://wadehuanglearning.blogspot.com/2019/05/commit-commit-commit-why-what-commit.html)
2. Create a pull request and name it with the status and the same name as the branch. E.g. [WIP] feat-post-smart-contract
3. Once the development is done, you can ask for a review. The PR can be merged after approval by **at least one other team member**.
## Steps for creating good issues.
1. When encountering an issue while developing, ensure the branch is pushed. (so that people can see what exactly you're working on)
2. Create an issue and mention the issue in the corresponding pull request.
3. Assign the person who can solve the issue with you. (If you don't know who to assign to, go to our discord and share the issue)
1. When encountering an issue while developing, ensure the branch is pushed. (so that people can see what exactly you're working on)
2. Create an issue and mention the issue in the corresponding pull request.
3. Assign the person who can solve the issue with you. (If you don't know who to assign to, go to our discord and share the issue)