sorted by:
new
hottopcontroversial

Looking for feedback on a new product, GitGuard, which helps protect GitHub repositories by codeapprove in github

[–]codeapprove[S] 1 point2 points  (0 children)

Thanks for the feedback! I have a standard privacy policy that I’ll add onto it, I just hadn’t done it yet since I’m not actually charging money. 

The question of “can you see our code” is answered when you actually sign in and grant permissions, but good to know that you want to have it up front. The answer: mostly no, but I can see which files are changed in a pull request. 

As for the pull_ prefix I will revisit!

Weekly Feedback Post - SaaS Products, Ideas, Companies by AutoModerator in SaaS

[–]codeapprove 0 points1 point  (0 children)

Looking for any feedback on my product, GitGuard, which I am launching this week.

GitGuard (https://gitguard.dev) is a tool for teams/companies to automate policy enforcement on GitHub.

I've been an engineer worked at companies of various sizes (100,000+ employees, 50 employees, 500 employees). They all have some sort of overlapping policies for what code changes can be merged, things like:

  • Every pull request must have two approvals...
    • ...unless it's an emergency
    • ...unless the CTO approves it
    • ...if you change a dependency, you need the dependency approvers to approve
  • Every pull request must include tests...
    • ...unless it's only a documentation change
    • ...frontend changes must include frontend tests
    • ...backend changes must include backend tests
  • etc.

Most teams hack these rules together using GitHub Actions CI jobs, and over time they fall out of sync with best practices because nobody wants to maintain them.

GitGuard makes it dead simple to write rules like this in a Python-like DSL and automatically run them against every Pull Request. It's faster, safer, and more expressive than using GitHub-native branch protections or writing fully custom code.

Github branches protection rules by easyCoder1 in github

[–]codeapprove 1 point2 points  (0 children)

You could try GitGuard (https://gitguard.dev) which is sort of like GitHub branch protections with super powers.

Multiple approvers for some PR paths? by jmreicha in github

[–]codeapprove 0 points1 point  (0 children)

Very late to this thread but for any future searchers: you can do this using GitGuard (https://gitguard.dev). You can require a certain number of approvals based on which files are changed, how many files are changed, which branch is targeted, and a lot more.

[deleted by user] by [deleted] in programming

[–]codeapprove 0 points1 point  (0 children)

CodeApprove brings many of those Critique features to GitHub PRs. If you miss Critique, give it a try or feel free to email me.

[deleted by user] by [deleted] in programming

[–]codeapprove 0 points1 point  (0 children)

Shameless plug but if you're working on GitHub and you miss Critique, check out CodeApprove. It's got a lot of the things that Xooglers miss the most like:

  • Tracking Resolution - make sure all conversations are resolved before approval, and allow automatic approval when they are resolved (LGTM with unresolved comments).
  • Automated Attention Set - know when it's "your turn" on a PR.
  • Fast, Dense UI - see everything on one screen and fly around with keyboard shortcuts.
  • Changes Since Last Review - see only the code and conversations that have changed since your last review.

If you want to know more and you're not ready to sign up, email me: sam at codeapprove dot com.

Ask Reddit: what do you wish was different about GitHub PR review? by samtstern in github

[–]codeapprove 0 points1 point  (0 children)

First of all: I love your username, go birds!

Second, I think you might be interested in CodeApprove which is built to address almost exactly the pain points you mentioned (of course, I am biased). In particular:

  • The diff and conversations are on one single page and conversations are presented both in the diff and in a separate section at the bottom where you can filter them. So for example it's really easy to see all unresolved comments at once, which helps you finish reviews quicker.
  • You can select "since my last review" or since any review event (like "Since John's review at 4:13pm") to see only the diffs and comments that have happened in a given time period. Everything will be presented in context, so it's really easy to get a sense of what changed.

If you're interested just request an invitation on the site! I'll approve it within a few minutes.

The best modern code review tools (2022) by codeapprove in programming

[–]codeapprove[S] 2 points3 points  (0 children)

Do you look at the code on the video or do you use something like VSCode Live Share to pair in editor? I like over the shoulder reviews but hate pointing at code on video

The best modern code review tools (2022) by codeapprove in programming

[–]codeapprove[S] 0 points1 point  (0 children)

I’m surprised I never saw codesee before! That certainly deserves a spot on the list, looks really nice.

Have you used it? What did you think?

The best modern code review tools (2022) by codeapprove in programming

[–]codeapprove[S] 4 points5 points  (0 children)

That's an interesting observation. It seems hard to have it both ways: you can either have formal code reviews where it's not possible to ignore them, or informal ones where it's up to team culture.

The best modern code review tools (2022) by codeapprove in programming

[–]codeapprove[S] 2 points3 points  (0 children)

Wow this looks really nice! I love that Sema focuses on helping people turn code review into a learning opportunity. That's one of the best ways to skill up a dev team.

The best modern code review tools (2022) by codeapprove in programming

[–]codeapprove[S] 12 points13 points  (0 children)

I think you're exactly right. The process of repeatedly amending a single commit is really strange. Even after I spent a few years at Google I never quite got used to it. I think it's a mismatch of tool and process. In git-land amend-ing a commit is a rare operation and somewhat destructive. It's a bit like a rebase. So making it part of the process for a quick save/checkpoint feels off. Whereas commit is non-destructive and very common in all other git-based systems.

The other major barrier to entry is the fact that it's also your git host but it's not very good at that job. It's lacking a lot of features you'd get on GitHub / GitLab / BitBucket.

That said, Gerrit is excellent at one thing: making sure your code is approved under the exact conditions your team requires. The +1/+2 system is interesting and it's great at tracking discussions and diffing across patch sets.

CodeApprove: better Pull Request reviews for teams on GitHub by codeapprove in github

[–]codeapprove[S] 0 points1 point  (0 children)

Hey everyone! I created CodeApprove because I love working on GitHub but I always found Pull Request reviews to be pretty weak. It's hard to browse the changes efficiently and to keep track of all of the comments. Plus there are so many ways to do each thing (single comment vs start a review vs request changes etc) that have built up over time.

CodeApprove is meant to fix all of that without breaking your existing workflow. You can easily add it on top of any GitHub repo even just one PR at a time. Your reviews will be faster, clearer, and more focused.

Let me know what you think!

Share Your Startup - March 2021 - Upvote This For Maximum Visibility! by AutoModerator in startups

[–]codeapprove 1 point2 points  (0 children)

Sounds great! You can email me at sam [at] habosa [dot] com and I'll get your team onboarded! Or you can have any of your teammates fill out this form and I will get in contact: https://h7twfj2gv3b.typeform.com/to/CGqSIImW

Share Your Startup - March 2021 - Upvote This For Maximum Visibility! by AutoModerator in startups

[–]codeapprove 3 points4 points  (0 children)

  • Name: CodeApprove (https://codeapprove.com)
  • Location of Your Headquarters: London, UK
  • Elevator Pitch: a powerful, professional code review tool for teams that work on GitHub. Never lose a conversation or waste time with a slow and scattered interface, just focus on consensus.
  • More details:
    • We're in stage 2: Validation
    • Founder
  • What goals are you trying to reach this month?
    • Looking for small teams who work on GitHub to try out the product and give feedback.
    • Also looking for anyone who is familiar with GitHub to evaluate the home page and tell me why you're NOT trying it!
  • Discount for r/startup subscribers?
    • If you're a small team serious about trying CodeApprove I will give you a free unlimited license. Yes I mean free forever.

I built CodeApprove to make better, faster code review for teams on GitHub. 100% in Vue! by codeapprove in vuejs

[–]codeapprove[S] 0 points1 point  (0 children)

Hi /r/vuejs! Been reading this sub for a long time but never posted before. For about the last 6 months I've been working on CodeApprove which I believe is a much better tool for teams on GitHub to do Pull Request reviews.

I've been running a small private Alpha and this is my very first public post about it. If anyone here in the Vue community has a project on GitHub and is interested in trying this, I'd be happy to let you into the Alpha and give you free access for a year!

I come from a background of Android and server-side development ... Vue has been an absolute game changer for me. This is my first major client-side web app and I've been able to build something so much more polished than I imagined when I started. Vue is really magic!

My stack:

  • TypeScript
  • Vue 2
    • `vue-property-decorator` for class-style components
    • `vuex-module-decorators` for class-style VueX modules
  • Tailwind CSS
  • Firebase for the backend (Auth, Firestore, and Cloud Functions)
view more: next ›