Please don't interfere with the native scrolling behavior.
Agreed. Autoscroll breaks the mobile experience horribly. Small text... No pinch to zoom... Half the text is always off the screen in landscape...
Show HN: GitMagic – Enforce your GitHub contribution guidelines
31–40 of 42 posts
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#32Please don't interfere with the native scrolling behavior.
And don't interfere with the "back" button, either. Scrolling back to the previous location isn't what anyone intends when they press it.
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#33Between Hound and Travis... I don't really see a use case for this... yet.
Travis is mainly for running tests and would require you to write your own validations. And I'm not sure if they have support for validating the descriptions of PRs and issues? Hound looks awesome! But it's only for code style validation. GitMagic will enforce contributing guidelines such as how to write commits, branches, what to include in PR descriptions, issues, and even file structure/naming conventions.
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#34Man, this really should be a default functionality of github itself.
That would be nice, so help us show what GitHub can be!
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#35My main feature request would be a way to enforce a PR must be a fast-forward merge. I tend to have a small set of words I prefix each git commit summary with (Add, Remove, Fix, etc). If I could verify summaries match that pattern that would be awesome. Also, if it is possible to enforce the guidelines specified in http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... I'd be so happy.
Great ideas, thanks! Sign up for our beta and we will do our best to make you happy :)
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#36Earlier quoted context omitted.
Any plans to have a tie-in for GitLab repos, as well?
Our plans is to begin with GitHub support only, since it is (at the moment at least...) the most popular service. But later we plan to support both GitLab and Bitbucket too.
Glad to hear you're planning to support GitLab, please let me know if you need any help.
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#37Earlier quoted context omitted.
Our plans is to begin with GitHub support only, since it is (at the moment at least...) the most popular service. But later we plan to support both GitLab and Bitbucket too.
Glad to hear you're planning to support GitLab, please let me know if you need any help.
Thanks, I will take you up on that!
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#38Please don't interfere with the native scrolling behavior.
I agree and disagree. As a general rule, you shouldn't be screwing with the scrolling behavior, but in case like this (with a slider-type of interaction), it is a bit more understandable. What I can't stand is when people do it just to affect the acceleration/whatever of scrolling as a gimmick. This has some usefulness at least and doesn't affect my experience negatively at all.
Personally, this infuriates me. I'm not done reading just because I started scrolling.
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#39Earlier quoted context omitted.
Any plans to have a tie-in for GitLab repos, as well?
Our plans is to begin with GitHub support only, since it is (at the moment at least...) the most popular service. But later we plan to support both GitLab and Bitbucket too.
Sweet action! Depending on how far you want to go with the Bitbucket integration, you could potentially inject warnings on the commit, branch, and pull request pages using the Bitbucket Connect framework.
One of our engineers wrote an add-on recently for enforcing some less automated aspects of CONTRIBUTING.md that you might be interested in too: https://blog.bitbucket.org/2016/01/26/pull-request-guideline...
Re: Show HN: GitMagic – Enforce your GitHub contribution guidelines
#40Earlier quoted context omitted.
It's a cloud service? I'm probably missing something, but it looks like a smallish git linter script? I guess I'm not seeing where all the work went to make this something more than an OSS script one could write in two hours.
Yes, I will look into how to make that a bit more clear :) This is integrating with GitHubs build checks and web hooks and we want it to be very easy to get started. A script could do local validation but that would require the contributor to actually run the script :P
There is a very well known Git guide named "Git Magic"
So you might be losing a bit of googlability wth that name.