A discord QA bot intended for learning purpose of JS Bootcamp study group

Hi everyone, I hope you can get onboard on this project easier, so I create a readme for contributing.

• Discord Question and Answer Bot
  • Table of Contents
  • Contributing
    • Step 1: Clone 🐑
    • Step 2: Checkout 💰
    • Step 3: Edit 🖊️
    • Step 4: Staging 🏋️‍♂️
    • Step 5: Push 🔝
    • Step 6: Make a Pull Request ✋
    • Step 7: Repeat ↩️
  • Contribute Easier and Faster
  • Contributor

Start contributing by forking this GitHub repo in your account! Fork button is on the top-right.

After you fork this repo, clone your fork to your local system. You can use GitHub desktop, VSCode or terminal to do this.

In VScode, click Ctrl + Shift + P and type clone, pick git clone, then paste your forked git address.

cd my-folder
git clone https://github.com/{{ your-username }}/discord-qa-bot.git

Download the zip file and extract it is also cloning so you can do that too.

Open your cloned folder then checkout to dev branch. This option can be seen in VSCode source control view Ctrl + Shift + G.

cd discord-qa-bot
git checkout dev

Edit the files and save. Add your name to contributor list if you want to!

After editing you can stage and commit your changes. Click + to stage your change on each files. Then commit it to dev branch by clicking ✅

git add README.md
git commit -m 'add my name to contibutor list'

Push your commit to your forked repository in GitHub by click ... then push.

git push origin dev

Last step on your part, open your GitHub repo. If your changes has been pushed correctly, you will see the Pull Request button. Make a pull request to dev branch of main repository.

And we are finally done.

You can contribute further by repeating Step 3 to Step 6. Sometimes you will find conflict between your fork and main repo due to other people has make changes to repo. You have to update your repo first by resolve conflict.

Forking makes git workflow a bit cumbersome but safer, you could join this team to get access to the dev branch directly. Please be careful on pushing to dev and main branch. It's better to make your own branch instead for safety purpose.

Access to this Repo team

You can push directly to dev if you think it's appropriate, but please make new branch for any big update so everyone can test first.

Contributor listed here in alphabetical order:

1. @zulvkr