Now I wonder how long before some of these features such as mandatory reviews will make it into Github Enterprise?
Announcing new tools, forums, and features
121–130 of 282 posts
Re: Announcing new tools, forums, and features
#122The inconsistent and non-sensical font and white space on the new profile pages is giving me an indescribable form of anxiety. If anybody out from the GH design team is out there, please put it back to how it was. :(. Example: https://github.com/Miserlou 10 font sizes is too many for any one page.
Re: Announcing new tools, forums, and features
#123This product video for GitHub Projects features a logo that's exactly like Trello's. Cold. https://youtu.be/NoBI4_9EuUw
Re: Announcing new tools, forums, and features
#124Earlier quoted context omitted.
It's only kind of open source, and only partly. They call it open core, so saying open source outright is a bit misleading. The review feature is very new in GL, and that plus all of the things you are mentioning within "everything in one spot" is available in this update (except maybe the coding env, not sure what that means anyway), if you've read the announcement. Github also has self hosting.
Where can I find a link about self hosted Github? Just curious to read about it.
Re: Announcing new tools, forums, and features
#125Earlier quoted context omitted.
It's only kind of open source, and only partly. They call it open core, so saying open source outright is a bit misleading. The review feature is very new in GL, and that plus all of the things you are mentioning within "everything in one spot" is available in this update (except maybe the coding env, not sure what that means anyway), if you've read the announcement. Github also has self hosting.
Where can I find a link about self hosted Github? Just curious to read about it.
Re: Announcing new tools, forums, and features
#126Earlier quoted context omitted.
> Open source* The Enterprise edition features[1] are closed source, and these aren't strictly "enterprise-y" features like SAML authentication. It includes plenty of "basic" workflow features found on GitHub: - Rebase merge requests before merge - Use fast-forward merges when possible - Create templates for issues and merge requests - Display merge request status for builds on Jenkins CI [1] https://about.gitlab.com…
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,…
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 and does the author get notified with a summary like the new GitHub code review feature? Because currently in GitLab the author does get a notification email for every line comment I make, which is also not really the perfect way of doing it.
I already know that Phabricator squashes the changes into one commit, I think I can live with that. (because it promotes small code reviews) Does Phabricator have any problems with git rebase, where I'm refreshing a feature branch with the most recent master state? What I really like about the merge/pull request workflow of GitLab is, that multiple developers can work together on one feature branch while a merge request is open and can be used as a discussion platform for the changes - is this possible with Phabricator?
Also I'm wondering how solid the issue tracking is, and if the project workboards can compete with Trello. Can it be used by non-developers without giving them access to the code?
Looking forward to test Phabricator tomorrow.
Re: Announcing new tools, forums, and features
#127Earlier quoted context omitted.
It looks like enforcing 2fa in an org (finally!) means anyone who doesn't have 2fa will be booted out (included whoever may be paying for it at the time) with an email explaining why. I'm afraid to tick the box because of this. :o/
Currently, we tell every new employee on joining the org to enable it, and review it a week later to ensure that they followed through. It is the exact same with Google Apps as well (where you add the user to the 2faexceptions group and review+remove them a week later). I was ready to flip the switch, till I realized that a third-party bot account in our organization doesn't have 2fa. Dropped them a mail, hoping to f…
Re: Announcing new tools, forums, and features
#128I sent this to support, but the "Files changed" tab in Pull Requests now has an announcement "We've made some change to reviewing code" The "Learn more" button on that banner is a broken link… (It's a good thing this HN post later directed me to the blog post, as now I've learned from that.)
Sorry about that! Is the link working now?
Re: Announcing new tools, forums, and features
#129Code reviews currently do not seem to come through on the webhooks at all. Our in-house automation suites depend on it, so this is a big do not use for us. I really wish their APIs weren't second class citizens. It takes weeks or months for new features to show up in the API - if at all. I wish there was 1-1 parity with the API.
Given how much iteration we do after an initial ship like this, especially one with as much feedback as code review, we prefer shipping the API after things have solidified and settled down after the wide release.
Re: Announcing new tools, forums, and features
#130The inconsistent and non-sensical font and white space on the new profile pages is giving me an indescribable form of anxiety. If anybody out from the GH design team is out there, please put it back to how it was. :(. Example: https://github.com/Miserlou 10 font sizes is too many for any one page.