Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing new tools, forums, and features

github.com

Post reply on HN
Print view View original

221–230 of 282 posts

Re: Announcing new tools, forums, and features

#221

Post by supercoder »

terda12 wrote: post #211
old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

I disagree, I have zero problems with these new features, which cost no extra money to me. These are all extra features, that I can choose to use or not use, that github rolled out for its users. I personally treat repositories as a single self contained code project, and I find that a lot of other people do too. The home page makes me feel less lonely. It's all good for me. Yeah a repo-centric trello board won't ser…

They definitely cost you money if you're paying for the product. Otherwise if they weren't developing new things they could lower the price

Re: Announcing new tools, forums, and features

#222

Post by rickhanlonii »

sgarrity wrote: post #16

Some nice improvements here. It appears, though, that Projects suffer from the same problem we've had with Issues: they are limited to one repo. I know there are some tools to manage Issues across repos, but for the most part, the tools seem to assume you work on only one repo, or that milestones only affect a single repo. I would love to see projects/milestones become more capable when dealing with cross-repo issues…

For what it's worth, I've had success browsing issues accross repos using the https://github.com/issues page. E.g. to view all issues that are in both redux and react-redux:

https://github.com/issues?q=repo%3Areactjs%2Fredux+repo%3Are...

Re: Announcing new tools, forums, and features

#223

Post by SEJeff »

moby wrote: post #121
SEJeff wrote: post #92

Now I wonder how long before some of these features such as mandatory reviews will make it into Github Enterprise?

The updated Code Review features will be coming to GitHub Enterprise soon - we always aim to get new features onto the Enterprise platform on the next major release (which occurs every 3 months on average).

Thanks, our team was literally lamenting about lacking specific reviewers when migrating from phabricator to github enterprise last week. Looking forward to it!

Re: Announcing new tools, forums, and features

#224

Post by tootie »

tyre wrote: post #201
sytse wrote: post #190

Earlier quoted context omitted.

I agree that putting projects under repositories looks counterintuitive. In BitBucket you have multiple repositories under one project https://confluence.atlassian.com/bitbucket/projects-79249795... We at GitLab are trying to keep it simple by having only one repository, one wiki, one issue tracker, one CD pipeline, and one set of milestones per project. Projects always below to a group. We aggregate on the group lev…

Meta-comment: As a founder and engineer, I used to give a lot of shit to Social Media as a growth channel. GitLab staff are "on point" by commenting on anything relevant to their industry (code creation/management) where their target customers are (HN). To other founders, this is what good marketing looks like.

If your product targets developers, commenting on HN seems like a pretty high value channel compared to something like facebook.

Re: Announcing new tools, forums, and features

#225

Post by tootie »

captn3m0 wrote: post #17

This is a rough summary of what all I read in the blog post: 1. projects. replaces trello, waffle.io, zenhub and many other similar services. 2. code reviews allow approval/request changes as sunny's screenshot shows 3. reviews can be made mandatory. 4. github platform integrations is getting a roadmap 5. a graphql api to query their database 6. enforce 2fa in organizations (much love for this one) 7. summarized time…

This all seems like baby stuff compared to Atlassian though. JIRA, Confluence, Bitbucket, HipChat. That's hard to beat.

Re: Announcing new tools, forums, and features

#226

Post by aidenn0 »

jsmthrowaway wrote: post #187
Nimimi wrote: post #97

Earlier quoted context omitted.

Take a look at Phabricator. It's a former Facebook project and been battle-tested at very large companies for years now. Huge open source projects like Blender, Haskell, Wikimedia and LLVM use it since it's the best open source code review tool and issue tracker. Wikimedia had a lengthy decision process and thoroughly vetted the alternatives. It has many enterprise features including code ownership, issue templates,…

Phabricator is also pretty amusing in terms of UX (by default), which is helpful when dealing with things that tend to anger folks -- like spirited reviews. I've often wondered if the sense of humor is half fun, half intentional in terms of psychologically making tedious work better for all involved. Even if accidental it's a nice thought. Based on my experience, Phabricator has some quirks but is quite solid, and th…

Even the configuration option for turning that off is amusing ("Serious Business" IIRC)

Re: Announcing new tools, forums, and features

#227

Post by aidenn0 »

superuser2 wrote: post #213
chrizel wrote: post #126

Earlier quoted context omitted.

I'm evaluating GitLab at work currently - primarily for its code review features and really like it. Read a lot about Phabricator yesterday as a possible alternative, and am considering testing it. I wonder how it compares to GitLab. Is it possible to set up protected branches, where I can say, only users X and Y are allowed to push to the master branch? Can I do a code review and then finalize it when I'm finished a…

>Is it possible to set up protected branches, where I can say, only users X and Y are allowed to push to the master branch? Yes. I recommend (and my employer uses) a Herald rule that admits pushes to master only if the changes are in an approved Diff (unit of code review). This way you get an enforced 2-man rule, but anyone besides the author can approve the change. This is currently impossible with Gitlab AFAIK, and…

> It is NOT a merge/pull-request workflow. It treats Git more like Subversion; Phabricator is a very sophisticated alternative to emailing patches around before SVN committing them (basically the equivalent of landing).

Due to popular demand, they are adding some tools to allow merge/PR workflow. That being said, it was not stable last time I checked (~6 mo. ago), and it will probably take a while, if ever, for it to be as good as what's already there for Differential (the current code-review/landing system).

That being said, their existing tools are really good, and the fact that you are not married to a single VCS is really nice. You can have some legacy SVN repositories and be fine, and use the exact same interface for code-review and landing as in your shiny new git repositories. Prefer hg to git? No problem. Have some complicated gitolite setup you don't want to bother migrating? Phabricator works fine even when not hosting the repository.

Re: Announcing new tools, forums, and features

#228

Post by aidenn0 »

rtpg wrote: post #186
bentlegen wrote: post #133

Earlier quoted context omitted.

I used Phabricator at a former employer, and it was one of the best software tools I've used. I'm always flabbergasted that it doesn't have more mindshare, especially when it's used internally at Facebook.

it's either self-hosted or at least $20/user/month. This alone makes it a bit of a hard ask for smaller companies at first, even for just kicking the tires.

It's worth noting that the first 30 days are free, and all 3 source control systems it offers have fairly painless synchronization, so there's low risk IMO.

On top of that it was really painless to install locally. I had it setup in under an hour, and that included my first time ever setting up my webserver with php, and first time configuring a mysql instance.

Re: Announcing new tools, forums, and features

#229

Post by luikore »

old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

One project with multiple repos just adds unnecessary work of integration and management. Or, your definition of project is something big, vague and blurry.

Some people are eager to divide their project into multiple repos in spite of git being a distributed version control system. Having many teams doesn't mean you should have many repos. Why not just let your team work on one small directory inside the repo?

Re: Announcing new tools, forums, and features

#230

Post by reustle »

toddsiegel wrote: post #87
jglovier wrote: post #32

Earlier quoted context omitted.

Great idea. Thanks!

While I have your attention. A few thoughts on code reviews. It's be nice if 1) approvals somehow show up on the pull requests index page, 2) create a notification within GH, 3) send an email. Right now you have to go to the PR page itself to see approvals. Edit: I saw an approval email notification on one PR, but not another. Thanks!

+1 for seeing approvals visually on the pull request index page. I currently use a "Reviewed" label with my team, and unfortunately we still have to even with this feature.
Post reply on HN