Add GitClear PR tool to list of code review tools #13
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -8,8 +8,8 @@ Feel free to contribute your suggestions. | |||||||||
|
|
||||||||||
| | Tool | Description | | ||||||||||
| | ---- | ----------- | | ||||||||||
| | [Gitpod](https://gitpod.io/) | Always ready to code - spin up fresh, automated dev environments for each task, in the cloud, in seconds. Gitpod is an open-source developer platform automating the provisioning of ready-to-code developer environments. | | ||||||||||
| | [GitClear Pull Request Review](https://www.gitclear.com/best_github_alternative_pull_request_review_tool) | A pull request tool inspired by Github's review tool that recognizes several types of code operations ("moved," "find/replace," "copy/paste") that reduce "lines to review" by 20-30% [in published research](https://www.gitclear.com/research_studies/pull_request_diff_methods_comparison_faster_review). The tool also identifies AI-generated code and offers an explanation for each changed line by hoving on the line, plus Slack notifications for "stuck" PRs. | | ||||||||||
|
There was a problem hiding this comment. Typo: "hoving" should be "hovering".
Suggested change
There was a problem hiding this comment. ⚪ LOW RISK Suggestion: Typo: 'hoving on the line' should be 'hovering on the line'. Also, please use the standard capitalization for 'GitHub'.
Suggested change
Author
There was a problem hiding this comment. I'm not sure if you'd really like a test that retrieves the URLs specified by the new addition, but if so, let me know? Especially if there is any prior art for testing the URL connections in the README, I'd be happy to piggyback off the existing precedent. If not, and you think it's important, I can add a new test file to iterate over the links in the table? Let me know how we can be most helpful to provide adequate proof that these links are accessible links for those who want to understand one of the more widely written-about Github PR alternatives. 🙏 |
||||||||||
| | [Pull Reminders](https://pullreminders.com/) (from Pull Panda) | Review and merge pull requests faster with Slack reminders and notifications. | | ||||||||||
| | [Pull Assigner](https://pullpanda.com/assigner) (from Pull Panda) | Pull Assigner assigns code reviews to make your process more balanced and efficient: 1) Organize reviewers into groups using GitHub Teams 2) Assign pull requests to teams or automate it with CODEOWNERS 3) Pull Assigner auto-assigns one or more members of the team as reviewers. | | ||||||||||
| | [Gitify](https://www.gitify.io/) | Gitify is all about making your life easier. Sitting on your menu bar, it informs you of any GitHub notifications without being annoying and of course without adverts. It just gets the job done. Works with GitHub and GitHub Enterprise. You can even connect multiple accounts. | | ||||||||||
|
|
||||||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo/casing: use the official "GitHub" capitalization in this description ("GitHub's" instead of "Github's").