If you want to proceed reading about
PLAIF Inc.
in Korean, please visit the Korean version.
This is a repository that stores materials about PLAIF. This repository documents the following contents:
- About
PLAIF
- Teams & Members
If you are reading this section, you must be a new member of PLAIF. We are honored to have you with us! We would like you to introduce yourself to the other members so that we can get to know you better. Here are some tips on how to do that.
Please write a self-introduction page using Markdown. Feel free to write about your job, the tools you use, and your interests. If you are stuck, you can refer to the following example and make a few changes. Here are the steps on how to write a self-introduction page.
Clone
this repo (ex.git clone https://github.com/plaif-dev/.github.git
)- Create a
branch
on which to work on the introduction ( ex.git switch -c jusung/introduction
) - Create a
Markdown
file with your name in themembers/
directory of the team you are in under the/profile/
directory (e.g.profile/software/members/jusung.md
).- If you cannot find your team, create a directory with the name of your team and configure the directory with the following structure.
team name
├─ team name.md
└─ members/
└─ your name.md
- Write your introduction in the Markdown file
- Link the newly created page to the team page (
e.g.
profile/software/software.md
) using a relative path.
Done writing your introduction? You are almost there. To double-check your work, the next step is to request peer reviews. There might be some typos! The following is the method that we use - check it out! (We follow the standard GitHub flow, as delineated below 😊.)
Commit
Introduction ( e.g.git commit -m "📝docs(introduction): add intro for someone"
)Push
Introduction (e.g.git push origin jusung/introduction
)- Send a
Pull Request
for peer reviews ( e.g. Web Pull Request)
<!--Template for reference-->
## Details
* add a readme page for `your-name`
## Checklist
Please double-check that your Pull Request complies with the following requirements:
- [ ] 😊 Declarative commit message.
- [ ] 💯 No typos.
- Repeat steps 1 and 2 if any modifications are necessary
- Get all required approvals from at least 2 team members
Got all the approvals you need from your team members? If so, please merge it so that everyone can see it. If you have all necessary approvals, the Merge button will be enabled in green at the bottom of the Pull Request. Click the button to merge it into the main branch. Don't forget to delete the branch you were working on after merging!