GitHub CLIが1.0に到達、CI/CDワークフローのスクリプト作成を可能にする

昨年2月にベータ版でリリースされたGitHub CLIがバージョン1.0になった。GitHubによると、問題 (issues) からレビュー、リリースまでのワークフロー全体にGitHub CLIを使用できる。さらに、GitHub APIをスクリプト化して、使用可能なアクションを自動化できる。

GitHub CLIの一般的なワークフローは、gh issue list または gh issue list --assignee <name> を実行して、未解決の問題を一覧表示することから始まる。gh issue コマンドは、その出力をフィルタリングするためのいくつかのオプションを提供する。たとえば、gh issues list --label "critical" を使用して critical の問題のみを表示したり、gh pr list --state closed を使用して closed の問題を表示したりできる。

問題の修正が完了したら、gh pr create を使用してプルリクエストを作成できる。これにより、必要なすべての情報を提供するように求められる。

プルリクエストを承認するために、共同作業者は gh pr checkout <#PR> を実行し、gh pr diff を使用して差分を表示し、gh pr review を使用してレビューを提供できる。実際、この初期の段階では、PRをレビューするためのGitHub CLIサポートはごくわずかである。具体的には、コメントをインラインで書き込むことはできないが、この機能は、GitHub CLIロードマップ上にあり、問題を編集したり、リクエストをプルしたりすることができる。

#continuous integration #git #github #デベロップメント #ニュース

What is GEEK

Buddha Community

Working with GitHub Actions

GitHub has become one of the most widely used Source Code Repository. Its Distributed Version Control System helps the developers for faster development and Integration of their code. Recently, it launched GitHub Actions in beta which enabled developers to create automated workflows to build, test, and deploy their source code on GitHub.

In this article, we will discuss about GitHub Actions and how it can be used to build an automated software development life-cycle workflow.

Below are the things we will discuss in this article:

• About GitHub Actions
• Basic Concepts of GitHub Actions
• Demo on Using GitHub Actions
• Creating a workflow file
• Configuring the workflow file
• Running the workflow file
• Conclusion

About GitHub Actions

Using GitHub Actions, we can create custom workflows that will help to build, test, package, release or deploy the code without leaving the GitHub UI. It enables us to build Continuous integration and Continuous Deployment capabilities directly in our repository. Here are some important features about GitHub Actions.

**YAML based process: **The workflow is written in YAML. Hence it is easy to create, read and use the actions that make up the workflow.

**One Place for everything: **By using GitHub Actions, we can build and test the developed code directly in our repository. There is no need to worry about integrating the source code repository with other build and deployment tools. Everything can be done in one single place.

**Easy to integrate code: **Since enabling CI/CD directly in the repository is possible using workflows, creating merge requests(MRs), building, testing and integrating them become way more seamless.

#tech (re)view #build #cd #ci #ci-cd #github #github actions #gitlab-ci #gradle #java #test

How to Compare Multiple GitHub Projects with Our GitHub Stats tool

If you have project code hosted on GitHub, chances are you might be interested in checking some numbers and stats such as stars, commits and pull requests.

You might also want to compare some similar projects in terms of the above mentioned stats, for whatever reasons that interest you.

We have the right tool for you: the simple and easy-to-use little tool called GitHub Stats.

Let’s dive right in to what we can get out of it.

Getting started

This interactive tool is really easy to use. Follow the three steps below and you’ll get what you want in real-time:

1. Head to the GitHub repo of the tool

2. Enter as many projects as you need to check on

3. Hit the Update button beside each metric

In this article we are going to compare three most popular machine learning projects for you.

#github #tools #github-statistics-react #github-stats-tool #compare-github-projects #github-projects #software-development #programming

GitHub CLIが1.0に到達、CI/CDワークフローのスクリプト作成を可能にする

昨年2月にベータ版でリリースされたGitHub CLIがバージョン1.0になった。GitHubによると、問題 (issues) からレビュー、リリースまでのワークフロー全体にGitHub CLIを使用できる。さらに、GitHub APIをスクリプト化して、使用可能なアクションを自動化できる。

GitHub CLIの一般的なワークフローは、gh issue list または gh issue list --assignee <name> を実行して、未解決の問題を一覧表示することから始まる。gh issue コマンドは、その出力をフィルタリングするためのいくつかのオプションを提供する。たとえば、gh issues list --label "critical" を使用して critical の問題のみを表示したり、gh pr list --state closed を使用して closed の問題を表示したりできる。

問題の修正が完了したら、gh pr create を使用してプルリクエストを作成できる。これにより、必要なすべての情報を提供するように求められる。

プルリクエストを承認するために、共同作業者は gh pr checkout <#PR> を実行し、gh pr diff を使用して差分を表示し、gh pr review を使用してレビューを提供できる。実際、この初期の段階では、PRをレビューするためのGitHub CLIサポートはごくわずかである。具体的には、コメントをインラインで書き込むことはできないが、この機能は、GitHub CLIロードマップ上にあり、問題を編集したり、リクエストをプルしたりすることができる。

#continuous integration #git #github #デベロップメント #ニュース

Stay Safe on GitHub: Security Practices to Follow

gthen Access Controls

Implementing proper access control is one of the best practices for enhancing security, not only on GitHub but in every other environment where code security is imperative.

GitHub offers several options that users can employ to reduce the risk of improper exposure. But to start with, it is important to employ the least privilege model where users are only granted necessary permissions.

Here are some basic access control guidelines that you should follow:

• Restrict the creation of repositories to prevent users from exposing organization information in public repositories.
• Enable branch protection and status checks to ensure users can merge commits or manipulate branches safely.
• Allow or disallow forking private repositories to ensure users do not expose or share organizational code with unauthorized parties.
• Revoke access for all inactive users who are no longer part of the contributors.
• Review access rights to your GitHub projects periodically.
• Ensure users do not share GitHub accounts or passwords.
• Ensure every contributor uses two-factor authentication on their account.
• Rotate personal access tokens and SSH keys

Never Store Credentials in Your GitHub Files

Leaking secrets to your GitHub repositories, either through code, configuration files, or commit messages, provides a gateway for attacks.

#tutorial #github #access control #software security #repository management #github issues #source code analysis #github apps #github enterprise #git best practices

Stay Safe on GitHub: Security Practices to Follow

GitHub is undoubtedly the largest and most popular social development platform in the world. According to its 2019 State of the Octoverse Report, GitHub is home to over 40 million, and the community keeps expanding every day.

As developers in this deeply interconnected community use open source code to build software, Github security should be a top priority. This is because extensive code re-use increases the risk of distributing vulnerabilities from one dependency or repository to another. As such, every contributor should focus on creating a secure development environment.

Here are eight security practices that GitHub users can follow to stay safe and protect their code:

Strengthen Access Controls

Implementing proper access control is one of the best practices for enhancing security, not only on GitHub but in every other environment where code security is imperative.

GitHub offers several options that users can employ to reduce the risk of improper exposure. But to start with, it is important to employ the least privilege model where users are only granted necessary permissions.

Here are some basic access control guidelines that you should follow:

• Restrict the creation of repositories to prevent users from exposing organization information in public repositories.
• Enable branch protection and status checks to ensure users can merge commits or manipulate branches safely.
• Allow or disallow forking private repositories to ensure users do not expose or share organizational code with unauthorized parties.
• Revoke access for all inactive users who are no longer part of the contributors.

#tutorial #github #access control #software security #repository management #github issues #source code analysis #github apps #github enterprise #git best practices