Introducing GitHub Enterprise ver.2.8!

DX business menu

DX business
HOME

Solution

Handling Manufacturer

event·
seminar

Document·
Case studies and columns

Inquiry

TOP

Products/Services

Specifications/Technical Information

Specifications/Technical Information
- GitHub - Specifications

User stories

support

Seminar content

Evaluation machine application/FAQ

Application for evaluation machine
- GitHub - Evaluation download
FAQ

Document request

inquiry

Introducing GitHub Enterprise ver.2.8!

2016/12/07 (Wed)

GitHub Enterprise ver. 2.8 was released in November 2016!
Here's a summary of the newly released features!
If you would like the full version, please contact us using the inquiry form.

(1) Functions for users
② Review function
③ How to use the review function
④Jupyter Notebooks
⑤Other functions for users
(6) Functions for administrators
⑦Others

(1) Functions for users

(1) Projects function added

It is now possible to create a Project (Kanban Board) in the Repository.
Manage projects visually.

(2) How to use the Projects function

Open Projects in Repository and create from New Project.
(In the future, it will be possible to create Projects for each Organization.)

Enter the name of the project.

Press Add column to add a column.

Press Add cards on the upper right to display Issue/Pull Request and add to coulmn with mouse operation. You can also add Issue/Pull Request/Card by mouse operation to move Card to other column.

② Review function

Improved review functionality.

You can also require a review.
You can collect comments to multiple places as one review.
For reviews, you can select the result from Approve, Request changes, and Comment, and you can specify whether the review result is OK or NG.
If the review result is Request changes, merge can be prevented until Approved.
A review button has been added in addition to the single comment to the source code in the conventional pull request.

You can also use the Protected Branch feature to require a pre-merge review. In the future, we plan to add a function to ignore reviews (Dismissing reviews) in an emergency.

By combining with the Branch Permission function, it is also possible to operate as a substantial approval flow so that only specific people can merge after review.

③ How to use the review function

Enter a comment and press Star a review.

It will be Pending once. If you have multiple comments, you can combine them into one review and send it as one notification.

Pressing the Finish your review button or Review changes on the upper right allows you to enter a Summary and status.

If the Protected Branch function requires review, it will be possible to merge once it is approved.

If the review raises a Request changes.

④Jupyter Notebooks

Added support for Jupyter Notebooks.

https://github.com/blog/1995-github-jupyter-notebooks-3

Jupyter Notebook is mainly for research institutions, academics, data science, Fintech, etc.
Papers, formulas, source code and images of execution results can be managed together as a single notebook.
Jupyter Notebook files with the extension ipynb can be rendered on GitHub Enterprise. Large ipynb files can be handled by Git LFS on GitHub Enterprise.

⑤Other functions for users

(1) User Profile has evolved

activity can be referenced.
You can browse by year.
It can also be used as a personnel database within the company.

(2) It is now possible to change the base branch after creating a pull request

(3) Wiki is now searchable

(4) License information is now displayed on the Repository

It will be displayed when files with names such as LICENSE or LICENSE.txt are placed directly under Repository.

(5)Milestones can now be prioritized

You can change the order of Issues associated with Milestones by mouse operation.

(6) Publish target of GitHub Pages can now be selected other than gh-pages branch

You can choose from gh-pages branch, master branch, under /docs of master branch.
It can be placed under master/docs, making it easier to manage code and documents.

https://github.com/blog/2228-simpler-github-pages-publishing

(7) 2FA (you can now enforce two-factor authentication for members joining your organization)

You can now enforce the use of two-factor authentication in your organization.
Two-factor authentication must be enabled in the built-in authentication scheme, not SAML.

(8) When rejoining an organization, the previous state can now be carried over.

Users rejoining an organization can now choose whether or not to return to their previous state (such as which team they were in at the time).
It can be selected when you add member to the Organization again.