Update index.html - Githubissues

acmpesuecc / calcyourgpa

It's a simple repository to enter your subjects and calculate your GPA.

MIT License

4 stars 16 forks source link

Open Vishwas1451 opened 3 years ago

Vishwas1451 commented 3 years ago

updated html file

Brief Description of Fix

Detailed Description including steps taken and any changes made

Linked Issue(s)
Closes #23 (Replace with Issue number)

chick-bot[bot] commented 3 years ago

Hi, @Vishwas1451! Thank you for your Pull Request 🥳🚀 A Maintainer will review your PR Shortly. Till then, hold tight!

aarav-babu commented 3 years ago

!bounty 20

chick-bot[bot] commented 3 years ago

Congrats @Vishwas1451 🥳🥳🚀🚀, you got 20 Bounty Points! Check out the Leaderboard to see your new score 😁

Vishwas1451 commented 3 years ago

updated html file

Brief Description of Fix

Detailed Description including steps taken and any changes made

Linked Issue(s) Closes #24 (Replace with Issue number)

aarav-babu commented 3 years ago

Please fork again and create a new PR for a different issue.

Vishwas1451 commented 3 years ago

i am not able to fork again. It is going back to the previously forked repo. What will I do??

aarav-babu commented 3 years ago

!bounty 30

chick-bot[bot] commented 3 years ago

Congrats @Vishwas1451 🥳🥳🚀🚀, you got 30 Bounty Points! Check out the Leaderboard to see your new score 😁

Vishwas1451 commented 3 years ago

My total bounty should be 50 right?? 20+30 I worked on 2 issues

aarav-babu commented 3 years ago

I already issued 20 bounty points for resolving issue #23. This is why separate Prs are better to avoid confusion.

Vishwas1451 commented 3 years ago

In leaderboard it is showing bounty points as 30 so can u give 50 bounty points at a stretch??

aarav-babu commented 3 years ago

!bounty 50

chick-bot[bot] commented 3 years ago

Congrats @Vishwas1451 🥳🥳🚀🚀, you got 50 Bounty Points! Check out the Leaderboard to see your new score 😁

avinash-vk commented 3 years ago

@Vishwas1451 for future ref, before working on the issue,

go to your fork, and make a new branch based off main. let the branch name be fix/36 or feature/22 depending on whether its a fix or a feature (or anything that'll help you connect back to the issue you're solving).
Work on that branch, and then submit a PR from that branch.
Now when working on the next issue, come back to the main branch, and create a new branch from main, so the changes made from your previous issue wont effect this. And when you're done making changes on the branch make another PR.