ruby-vietnam / hardcore-rule Goto Github PK

Source code: https://github.com/ruby-vietnam/hardcore-rule/tree/master/algorithms/collector

Background

• When starting the algorithm collector, it merges pull requests and add a comment to the weekly report page
  

Problems

• Sometimes, we need to test or verify features that we only want to check pull request scores and review final comments without merging or add any real comments.

Proposal

• Add a variable environment to declare testing mode, suggestion: DEBUG_MODE
• When DEBUG_MODE=true, the algorithm collector won't merge and delete any pull requests and add comments to the weekly report page
  
• Other functions to calculate scores, printing debug console work normally.

Show if a submission missed deadline or not in week-report. @tamnd

Every week, we pick algorithm problems to solve and post them to this ticket.
At 00:00 on Sunday (VN time), we run an automation tool to merge solution PRs and collect scores. The score report will follow the problems.

Mapping of GitHub account and slack account is defined in https://github.com/ruby-vietnam/hardcore-rule/blob/master/algorithms/PARTICIPANTS.md

The source code of the automation tool is in https://github.com/ruby-vietnam/hardcore-rule/tree/master/algorithms/collector

Mapping of problem's level and the score is defined in this issue content.

Weekly problems are posted in this issue follow the format:

Weekly Problem: Season x - Week y

<Level>: <URL>
Easy: https://leetcode.com/problems/two-sum/
Medium: https://leetcode.com/problems/generate-parentheses/

Level - Score mapping:

*** Score mapping ***
Easy: 1
Medium: 2
Hard: 3
*** End score mapping ***

Source code: https://github.com/ruby-vietnam/hardcore-rule/tree/master/algorithms/collector

Background

• Algorithm collector access Algorithm weekly report page to get "Weekly problems". It always expects the latest comment on the page as the latest problems of the current week.

Problems

• Sometimes, we have to discuss or add comments on Algorithm weekly report page that makes the latest comment on the page is not the latest problems comment.

Proposal

• When checking comments of Algorithm weekly report page, we check starting pattern "Weekly problem:" as first problems posts and assume it's problem's comments.
• Algorithm collector use the latest comment that starts with "Weekly problem:" and expect it as the latest problems comment. Other comments without starting of "Weekly problem:", we skip it.
• Trim space/tab to avoid typing problems.
• Allows custom starting problem patterns from the variable environments. Default is "Weekly problem:"

Create a github page for this repo. This can help people read and follow changes in this repo.

Introduce failure and remove all unwrap

To find out who missed out on that week.

Every week, we pick algorithm problems to solve and post them to this ticket.
At 00:00 on Sunday (VN time), we run an automation tool to merge solution PRs and collect scores. The score report will follow the problems.

Mapping of GitHub account and slack account is defined in https://github.com/ruby-vietnam/hardcore-rule/blob/master/algorithms/PARTICIPANTS.md

The source code of the automation tool is in https://github.com/ruby-vietnam/hardcore-rule/tree/master/algorithms/collector

Mapping of problem's level and the score is defined in this issue content.

Weekly problems are posted in this issue follow the format:

Weekly Problem: Season x - Week y

<Level>: <URL>
Easy: https://leetcode.com/problems/two-sum/
Medium: https://leetcode.com/problems/generate-parentheses/

Level - Score mapping:

*** Score mapping ***
Easy: 1
Medium: 2
Hard: 3
*** End score mapping ***

Last year report: #1408

Source code: https://github.com/ruby-vietnam/hardcore-rule/tree/master/algorithms/collector

Background

• When starting the algorithm collector, it calculates the score and merges pull requests.

Problems

• Few pull requests are created from UI GitHub that create un-deleted branches.

Proposal

• Delete pull request after calculating and merging

Source code: https://github.com/ruby-vietnam/hardcore-rule/tree/master/algorithms/collector

Background

• Algorithm collector will go through all "open" pull requests and do score calculations.

Problems

• Sometimes, "open" pull requests is not algorithm purpose. The algorithm collector counts it as a pull request of the weekly algorithm.

Proposal

• Only check pull requests that have changed files in a folder algorithm

Don't know how to use or develop the tool

PR's file should be located in /algorithms/solutions/<week_number>