Key Information

Register
Submit
The challenge is finished.

Challenge Overview

The prizes shown on the challenge page are only for reference. The actual payout will be based on bugs fixed and payments will be issued instantly when a fix is accepted. We're waiting for the feedback from clients, so we are expecting to add issues on a daily basis for the next one week so it's a good time to join this challenge! 

Challenge Overview

Git is the leading open source SCM (Software Configuration Management), our clients like the popular Git Diff VSCode extension GitLens for SCM. However, GitLens lacks some features that the clients need, so they want to add the missing functionalities into it. We would like to make this tool a much more valuable code review tool.

Now we have finished all functionalities requirements, there are some remain issues, we need to clean them up in this challenge.

How It Works:

1. You need to be registered Github and GitLab
2. The repo is public so everybody is able to access to it.
3. Go to the GitHub repo: https://github.com/billsedison/vscode-gitlens
4. The public GitHub repo has collaboration issues with Topcoder-X so I moved all tickets to GitLab. Please read this announcement  https://github.com/billsedison/vscode-gitlens/issues/1 
     -  Please use the following link to grant yourself access to the GitLab repo
https://x.topcoder.com/api/v1/gitlab/groups/registration/aa81096a-9319-45a3-8dce-7a52a0093890-1538750953636
     -  Please visit https://gitlab.com/aggregated-git-diff/aggregated-git-diff-bug-bash/issues to pick up any issues.
5. Go to the issue list and find an issue you wish to work. They will be labeled with tcx_OpenForPickup (Open for pickup). You can only work the issues with a label for “Open for pickup”.
6. 
When you find an issue, assign the issue to yourself, and change the label to tcx_Assigned (Assigned).  If you feel the issue amount is too low, please make a comment on the issue saying what you feel the dollar amount should be. If it's accepted by the copilot, upon review, the copilot will edit the issue to reflect the new amount.
7. Work the issue as normal, when you are done, change the label to tcx_ReadyForReview (Ready for review)
8. O
nce you mark the issue “Ready for review”, a copilot will review the issue and change it’s status appropriately.  Once the issue is marked as tcx_FixAccepted (Fix accepted), the system will automatically pay you the dollar amount specified in the issue title.

Note to developers:  

  • If you do not mark the issue as “Ready for review” within 24 hours, the issue will fall back to “Open for pickup” and anyone can pick the issue back up.  
  • If you need more time to work on an issue, leave a comment on the issue you want to work.
  • You have to assign issues on GitLab but create a pull request on GitHub for resolving issues. I'm really sorry for the inconvenience but this is the only way to work around the limits of GitHub and Topcoder-X at this moment. Thanks for your understanding.


Final Submission Guidelines

Please see above

ELIGIBLE EVENTS:

Topcoder Open 2019

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30072658