News for hackers. Stuff that matters.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by tyre on Friday February 12, 2016 @01:42PM (#11089393)
The API of your configuration could use some work. Have you looked at the validations present in JSON Schema[1]?

Instead of

  {
    "commit": {
      "message_must_be_imperative_tense": true,
      "message_must_include_prefix": {
        "prefixes": ["feat", "fix", "docs", "refactor"],
        "require_after_prefix": " "
      }
    }
  }

Something like:

  {
    "commit": {
      "message": {
        "imperative": true,
        "prefixes": ["feat ", "fix ", "docs ", "refactor "]
      }
    }
  }
[1] http://json-schema.org/latest/json-schema-validation.html
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @01:51PM (#11089461)
Thanks for the feedback. The JSON structure is something we will refine, and right now we wanted to have very explicit rules and not too complex configuration settings. But we will evaluate this along the way, and I like your example :)
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by fiatjaf on Saturday February 13, 2016 @12:16PM (#11094725)
I like "message_must_be_imperative_tense" much more. It is much clearer. it doesn't hurt to be so big since you're going to set it up just once.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by l-p on Friday February 12, 2016 @01:40PM (#11089368)
Please don't interfere with the native scrolling behavior.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by thisisdave on Friday February 12, 2016 @03:05PM (#11090104)
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 guid... by atom-morgan on Friday February 12, 2016 @02:05PM (#11089584)
Please! Maybe I'm weird but sometimes I simply want to reposition text on my screen. Just a slight adjustment, think eye level, so it's a bit easier to read and sites like this don't allow me to do so.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by andyfleming on Friday February 12, 2016 @02:30PM (#11089809)
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.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by lojack on Friday February 12, 2016 @04:01PM (#11090556)
Personally, this infuriates me. I'm not done reading just because I started scrolling.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by jc4p on Friday February 12, 2016 @02:21PM (#11089727)
Or at least use `replaceState` not `pushState`. I scrolled from the top of the page down one section and when I hit back it just went right back to the top of the page.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by karlkfi on Friday February 12, 2016 @02:40PM (#11089877)
Agreed. Autoscroll breaks the mobile experience horribly. Small text... No pinch to zoom... Half the text is always off the screen in landscape...
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @01:53PM (#11089472)
I usually don't like forced scroll myself, but I have to say that I'm personally satisfied with the results of this site.

But I hear you and when the site goes from landing page to real website we will make sure to have a nice scroll experience for everyone :)

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by unfunco on Friday February 12, 2016 @02:30PM (#11089807)
A "nice scroll experience" is no scroll experience, don't even think about the scrollbar, it's the concern of the browser.

Good design is unobtrusive. [5]

Good design is as little design as possible. [10]

[5, 10]: https://www.vitsoe.com/us/about/good-design

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by icholy on Friday February 12, 2016 @01:55PM (#11089486)
It breaks the back button.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by michaelmior on Friday February 12, 2016 @01:31PM (#11089299)
> Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread.

AFAICT, there's nothing to try yet.

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by detaro on Friday February 12, 2016 @02:24PM (#11089756)
> For example, blog posts, sign-up pages, and fundraisers can't be tried out, so they don't count as Show HNs.

indeed.

https://news.ycombinator.com/showhn.html

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by danielrw7 on Friday February 12, 2016 @01:21PM (#11089211)
It took me a while to figure out that there was a second page with no scrollbar and a non-obvious arrow.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by dkubb on Friday February 12, 2016 @02:25PM (#11089766)
I saw this comment and then started looking for a link to a second page. It turns out I was able to "swipe up" on my magic mouse to scroll down to the second page.

I'd strongly recommend that the developer stop hiding the scrollbar.

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by StavrosK on Friday February 12, 2016 @02:13PM (#11089664)
Oh, there's a second page! Thanks for that.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @02:22PM (#11089739)
I just made the arrow a little larger, might not be enough but it's a start. Later I would like to move to a more traditional site.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by StavrosK on Friday February 12, 2016 @02:24PM (#11089757)
Hmm, which arrow? I don't see one.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @02:00PM (#11089523)
I will try to make it more visible, thanks!
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @12:47PM (#11088950)
Tired of all the GitHub drama? We're close to launching GitMagic to fix some of that. If you have any questions, please ask, we’re happy to answer them :) And all feedback are appreciated.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by cobrabyte on Friday February 12, 2016 @02:08PM (#11089607)
Any plans to have a tie-in for GitLab repos, as well?
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @02:28PM (#11089792)
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.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by kannonboy on Friday February 12, 2016 @04:02PM (#11090560)
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 guid... by gitmagic on Friday February 12, 2016 @04:36PM (#11090834)
Thanks, that sounds really cool and would definitely be something we will look into pretty soon :)
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by sytse on Friday February 12, 2016 @03:40PM (#11090361)
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 guid... by gitmagic on Friday February 12, 2016 @03:52PM (#11090474)
Thanks, I will take you up on that!
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by dkubb on Friday February 12, 2016 @02:31PM (#11089820)
My 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.

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @03:14PM (#11090169)
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 guid... by killercup on Friday February 12, 2016 @01:30PM (#11089292)
Cool. I've wanted to try GitCop (which seems to do something similar) for a while, but didn't get around to it yet.

> Magically enforce your GitHub contribution guidelines.

Looks pretty non-magical and quite straightforward to me. I even get to set explicit rules. Why the 'magic' branding?

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @01:57PM (#11089509)
I'm glad to hear that you get our message! The 'magic' branding is there because everything is done automatically (i.e. it's a cloud service) without the need to install anything on the client side.

And we love magic ;)

Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by StavrosK on Friday February 12, 2016 @02:16PM (#11089691)
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.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @02:25PM (#11089765)
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
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by emmelaich on Friday February 12, 2016 @04:12PM (#11090643)
There is a very well known Git guide named "Git Magic" So you might be losing a bit of googlability wth that name.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by fiatjaf on Friday February 12, 2016 @01:23PM (#11089228)
That seems great, but the name doesn't really mean what the service does.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @02:02PM (#11089553)
Thanks! We decided to not pick a too specific name (like something with "contributing"), since in the future we want to provide services that automates other types of tasks related to working with git. Hence the "GitMagic" name :)
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by rrrx3 on Friday February 12, 2016 @02:38PM (#11089861)
Man, this really should be a default functionality of github itself.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @03:11PM (#11090146)
That would be nice, so help us show what GitHub can be!
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by OhSoHumble on Friday February 12, 2016 @01:57PM (#11089501)
Between Hound and Travis... I don't really see a use case for this... yet.
Re:Show HN: GitMagic – Enforce your GitHub contribution guid... by gitmagic on Friday February 12, 2016 @03:08PM (#11090129)
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.