1619687475
Our project data is accessible via GitHub’s comprehensive REST and GraphQL APIs, so we can use Actions to manage work for us!
Hello from the GitHub Docs team! We build everything you see at docs.github.com. Over the past year, we’ve written a bunch of GitHub Actions workflows to do some fun automation that saves us time and effort. We thought folks might be interested in a peek under the hood.
If you’re new to GitHub Actions, get started at https://docs.github.com/en/actions.
Our docs content and tooling are all open source, so you can check out our full suite of workflow files in https://github.com/github/docs/tree/main/.github/workflows.
As the team responsible for documenting every aspect of GitHub, as well as managing open source contributions from the community, we have a lot of work to track. But every minute (or hour…) we spend on manual project management tasks is one we don’t spend on important content or site improvements that benefit users.
Fortunately, because we use GitHub issues and project boards to manage our work, our project data is accessible via GitHub’s comprehensive REST and GraphQL APIs. This means we can write programs to manage work for us!
GitHub’s APIs existed long before Actions, but in the old days, you had to write scripts from scratch, hook up an Octokit library, or use a framework like Probot. While Probot is awesome, Actions does a lot more heavy lifting out of the box. Within a YAML workflow file, you can use github-script and the GitHub CLI to access the full power of GitHub’s APIs, find and use prebuilt actions from the Marketplace, or write your own action!
We’ve found we can spin up a workflow file in a fraction of the amount of time it would take us to write a new script or create an app. And the YAML format is friendly enough that every member of our team is empowered to contribute, not just engineers.
#github #git #developer #programming
1624347085
In this blog, we are going to learn how to create our own custom GitHub action using javaScript.
Automate, customize, and execute your software development workflows right in your repository with GitHub Actions. You can discover, create, and share actions to perform any job you’d like, including CI/CD, and combine actions in a completely customized workflow.
There are three types of actions: Docker container actions, JavaScript actions, and composite run steps actions.
Let’s create a Custom GitHub Action using JavaScript by creating a public repo, once the repo is created, we can clone it to our local machine using VS Code or GitPod. You need to have Node.js 12.x or higher and npm installed on your machine to perform the steps described here. You can verify the node and npm versions with the following commands in a VS Code or GitPod terminal.
node --version
npm --version
#github #github-tutorial #github-actions #github-trend
1617437520
I recently deployed my portfolio site and wanted to try out github actions and this is my experience of automating the deployment.
This article is more focused on how you can use the GitHub actions and how easy it is to deploy your code to GitHub pages rather than the portfolio site code.So every time you make an update or build to your website ,the changes are automatically reflected and this automated deploying process makes work much faster.
The way GitHub action works is you create actions in your repositories by creating one or more yaml files and these are called workflows.Workflows now can handle build tasks like CI CD. This means you use the action to test your code and push the site to the desired hosting platform (in this case GitHub pages ) when the main branch changes .
First step assuming that you have a GitHub account is to create a repository having your website code in it.Now I have a bootstrap website but in the future I do plan on adding node JS so I already added package.json.
#workflow #portfolio #github #github-actions #github-pages
1620871761
A short tutorial on how to deploy an Azure function using GitHub action.
As we know, GitHub Actions help us automate tasks, for example, executing an integration/deployment pipeline as we create a release, or running integration test scripts after pull request event, or maybe just simply an acknowledgment to a user who has created an issue against your repository.
Here, we will create a simple Github action to deploy an HTTP Trigger Azure function to Azure Function App.
Step 1, is to create a function app in Azure. I am not going into the details of how to create the function app. You can either use an easy self-guided** Azure portal** or Azure CLI to create a function app.
Once we have created a function app in Azure, one key thing we have to do is download its publish profile, as we will need it to deploy the function to the function app from GitHub.
One key thing to do here is add the below configuration parameter to configuration settings of the function app:
_WEBSITE_WEBDEPLOY_USE_SCM_
_ : __TRUE_
#github #github-actions
1603861600
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.
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
1603830240
It’s now even easier to review logs from your GitHub Actions workflow runs. We’ve introduced several improvements to make the experience more performant, precise, and pleasing to use.
When we think about successful automation, we aim to spend the least amount of time looking at what’s automated, so we can focus our attention on what’s relevant. But sometimes things don’t go as planned, and we are required to review what happened. That debugging process can be frustrating; that’s why we’re introducing a series of changes that will improve both performance and user experience:
#features #product #actions #ci/cd #github actions #github