Što su Github akcije i kako možete automatizirati testove i slack obavijesti?

Automatizacija je moćan alat. To nam štedi vrijeme i može pomoći u smanjenju ljudskih pogrešaka.

Ali automatizacija može biti teška i ponekad se može pokazati skupom. Kako Github Actions može ojačati naš kôd i dati nam više vremena za rad na značajkama umjesto grešaka?

• Što su Github akcije?
• Što je CI / CD?
• Što ćemo graditi?
• Dio 0: Postavljanje projekta
• Dio 1: Automatizacija testova
• Dio 2: Objavite nove zahtjeve za povlačenjem u Slack

Što su Github akcije?

Akcije su relativno nova značajka Githuba koja vam omogućuju postavljanje CI / CD tijekova rada pomoću konfiguracijske datoteke izravno u vašem Github repo-u.

Prije toga, ako ste željeli postaviti bilo kakvu automatizaciju s testovima, gradnjama ili implementacijama, morali biste potražiti usluge poput Circle CI i Travis ili napisati vlastite skripte. Ali s Akcijama imate prvoklasnu podršku moćnom alatu za automatizaciju vašeg radnog procesa.

Što je CI / CD?

CD / CD označava kontinuiranu integraciju i kontinuiranu implementaciju (ili može biti kontinuirana isporuka). Oboje su prakse u razvoju softvera koje timovima omogućuju brzu, učinkovitu i idealnu izradu projekata s manje pogrešaka.

Kontinuirana integracija ideja je da se, dok različiti članovi tima rade na kodu na različitim git granama, kôd spoji u jednu radnu granu koja se zatim gradi i testira automatiziranim tijekovima rada. To pomaže u stalnom osiguravanju da svi kodovi ispravno rade zajedno i jesu li dobro testirani.

Kontinuirano postavljanje čini ovaj korak dalje i dovodi ovu automatizaciju na razinu implementacije. Ako postupkom CI automatizirate testiranje i izgradnju, kontinuirano postavljanje automatizirat će implementaciju projekta u okruženje.

Ideja je da je kôd, nakon bilo kojeg procesa izrade i testiranja, u stanju za raspoređivanje, tako da bi trebao biti u mogućnosti implementirati.

Što ćemo graditi?

Riješit ćemo dva različita tijeka rada.

Prvo će biti jednostavno pokretanje nekih automatiziranih testova koji će spriječiti spajanje zahtjeva za povlačenjem ako ne uspije. Nećemo prolaziti kroz izradu testova, ali proći ćemo kroz tekuće testove koji već postoje.

U drugom dijelu postavit ćemo tijek rada koji šalje poruku u popuštanju s vezom na zahtjev za povlačenje kad god se stvori novi. Ovo može biti od velike pomoći kada s timom radite na projektima otvorenog koda i potreban vam je način za praćenje zahtjeva.

Dio 0: Postavljanje projekta

U ovom vodiču možete stvarno raditi na bilo kojem projektu koji se temelji na čvorovima sve dok ima testove koje možete pokrenuti za 1. dio.

Ako želite slijediti jednostavniji primjer koji ću koristiti, postavio sam novi projekt koji možete klonirati s jednom funkcijom koja ima dva testa koja se mogu pokrenuti i proći.

Ako želite provjeriti ovaj kôd za početak, možete pokrenuti:

git clone --single-branch --branch start [email protected]:colbyfayock/my-github-actions.git 

Jednom kada ste to klonirali lokalno i instalirali ovisnosti, trebali biste moći pokrenuti testove i vidjeti kako prolaze!

Također treba imati na umu da ćete morati dodati ovaj projekt kao novo spremište na Githubu kako biste ga mogli pratiti.

Slijedite uz predavanje!

Dio 1: Automatizacija testova

Testovi su važan dio svakog projekta koji nam omogućuje da osiguramo da ne radimo postojeći kôd dok radimo. Iako su važni, na njih je lako zaboraviti.

Možemo ukloniti ljudsku prirodu iz jednadžbe i automatizirati izvođenje testova kako bismo bili sigurni da ne možemo nastaviti bez popravljanja onoga što smo slomili.

Korak 1: Stvaranje nove akcije

Dobra vijest je da Github zapravo olakšava započinjanje ovog tijeka rada jer je to jedna od njihovih unaprijed ispečenih opcija.

Za početak ćemo krenuti do kartice Akcije na našoj stranici spremišta.

Kad stignemo, odmah ćemo vidjeti neke početne tijekove rada s kojima nam Github omogućuje ronjenje. Budući da koristimo projekt čvora, možemo nastaviti i kliknuti Postavi ovaj tijek rada u tijeku rada Node.js.

Nakon učitavanja stranice, Github će vas otvoriti u novom uređivaču datoteka koji već ima hrpu dodanih konfiguracijskih opcija.

Zapravo ćemo ovo ostaviti "takvo kakvo je" za naš prvi korak. Po želji možete promijeniti naziv datoteke u tests.ymlili nešto što ćete pamtiti.

Možete nastaviti i kliknuti Pokreni urezivanje, a zatim ga predajte u mastergranu ili dodajte promjenu u novu granu. Za ovo uputstvo ću se obvezati izravno na master.

Da bismo vidjeli našu novu akciju, možemo ponovno kliknuti karticu Akcije koja će nas vratiti na novu nadzornu ploču Akcije.

Odatle možete kliknuti Node.js CI i odabrati urezivanje koje ste upravo napravili gore i sletjet ćete na našu novu nadzornu ploču akcije. Zatim možete kliknuti na jednu od verzija čvora na bočnoj traci putem gradnje (# .x) , kliknuti na padajući izbornik Pokreni npm i moći ćemo vidjeti izlaz naših testova koji se izvode (što ako slijedite sa mnom, treba proći!).

Slijedite uz predavanje!

Korak 2: Konfiguriranje naše nove akcije

Pa što smo upravo učinili gore? Proći ćemo kroz konfiguracijsku datoteku i ono što možemo prilagoditi.

Počevši od vrha, mi navodimo naše ime:

name: Node.js CI 

This can really be whatever you want. Whatever you pick should help you remember what it is. I'm going to customize this to "Tests" so I know exactly what's going on.

on: push: branches: [ master ] pull_request: branches: [ master ] 

The on key is how we specify what events trigger our action. This can be a variety of things like based on time with cron. But here, we're saying that we want this action to run any time someone pushes commits to  master or someone creates a pull request targeting the master branch. We're not going to make a change here.

jobs: build: runs-on: ubuntu-latest 

This next bit creates a new job called build. Here we're saying that we want to use the latest version of Ubuntu to run our tests on. Ubuntu is common, so you'll only want to customize this if you want to run it on a specific environment.

 strategy: matrix: node-version: [10.x, 12.x, 14.x] 

Inside of our job we specify a strategy matrix. This allows us to run the same tests on a few different variations.

In this instance, we're running the tests on 3 different versions of node to make sure it works on all of them. This is definitely helpful to make sure your code is flexible and future proof, but if you're building and running your code on a specific node version, you're safe to change this to only that version.

 steps: - uses: actions/[email protected] - name: Use Node.js ${{ matrix.node-version }} uses: actions/[email protected] with: node-version: ${{ matrix.node-version }} - run: npm ci - run: npm run build --if-present - run: npm test 

Finally, we specify the steps we want our job to run. Breaking this down:

• uses: actions/[email protected]: In order for us to run our code, we need to have it available. This checks out our code on our job environment so we can use it to run tests.
• uses: actions/[email protected]: Since we're using node with our project, we'll need it set up on our environment. We're using this action to do that setup  for us for each version we've specified in the matrix we configured above.
• run: npm ci: If you're not familiar with npm ci, it's similar to running npm install but uses the package-lock.json file without performing any patch upgrades. So essentially, this installs our dependencies.
• run: npm run build --if-present: npm run build runs the build script in our project. The --if-present flag performs what it sounds like and only runs this command if the build script is present. It doesn't hurt anything to leave this in as it won't run without the script, but feel free to remove this as we're not building the project here.
• run: npm test: Finally, we run npm test to run our tests. This uses the test npm script set up in our package.json file.

And with that, we've made a few tweaks, but our tests should run after we've committed those changes and pass like before!

Follow along with the commit!

Step 3: Testing that our tests fail and prevent merges

Now that our tests are set up to automatically run, let's try to break it to see it work.

At this point, you can really do whatever you want to intentionally break the tests, but here's what I did:

I'm intentionally returning different expected output so that my tests will fail. And they do!

In my new pull request, my new branch breaks the tests, so it tells me my checks have failed. If you noticed though, it's still green to merge, so how can we prevent merges?

We can prevent pull requests from being merged by setting up a Protected Branch in our project settings.

First, navigate to Settings, then Branches, and click Add rule.

We'll then want to set the branch name pattern to *, which means all branches, check the Require status checks to pass before merging option, then select all of our different status checks that we'd like to require to pass before merging.

Finally, hit Create at the bottom of the page.

And once you navigate back to the pull request, you'll notice that the messaging is a bit different and states that we need our statuses to pass before we can merge.

Note: as an administrator of a repository, you'll still be able to merge, so this technically only prevents non-administrators from merging. But will give you increased messaging if the tests fail.

And with that, we have a new Github Action that runs our tests and prevents pull requests from merging if they fail.

Follow along with the pull request!

Note: we won't be merging that pull request before continuing to Part 2.

Part 2: Post new pull requests to Slack

Now that we're preventing merge requests if they're failing, we want to post a message to our Slack workspace whenever a new pull request is opened up. This will help us keep tabs on our repos right in Slack.

For this part of the guide, you'll need a Slack workspace that you have permissions to create a new developer app with and the ability to create a new channel for the bot user that will be associated with that app.

Step 1: Setting up Slack

There are a few things we're going to walk through as we set up Slack for our workflow:

• Create a new app for our workspace
• Assign our bot permissions
• Install our bot to our workspace
• Invite our new bot to our channel

To get started, we'll create a new app. Head over to the Slack API Apps dashboard. If you already haven't, log in to your Slack account with the Workspace you'd like to set this up with.

Now, click Create New App where you'll be prompted to put in a name and select a workspace you want this app to be created for. I'm going to call my app "Gitbot" as the name, but you can choose whatever makes sense for you. Then click Create App.

Once created, navigate to the App Home link in the left sidebar. In order to use our bot, we need to assign it OAuth scopes so it has permissions to work in our channel, so select Review Scopes to Add on that page.

Scroll own and you'll see a Scopes section and under that a Bot Token section. Here, click Add an OAuth Scope. For our bot, we don't need a ton of permissions, so add the channels:join and chat:write scopes and we should be good to go.

Now that we have our scopes, let's add our bot to our workspace. Scroll up on that same page to the top and you'll see a button that says Install App to Workspace.

Once you click this, you'll be redirected to an authorization page. Here, you can see the scopes we selected for our bot. Next, click Allow.

At this point, our Slack bot is ready to go. At the top of the OAuth & Permissions page, you'll see a Bot User OAuth Access Token. This is what we'll use when setting up our workflow, so either copy and save this token or remember this location so you know how to find it later.

Note: this token is private - don't give this out, show it in a screencast, or let anyone see it!

Finally, we need to invite our Slack bot to our channel. If you open up your workspace, you can either use an existing channel or create a new channel for these notifications, but you'll want to enter the command /invite @[botname] which will invite our bot to our channel.

And once added, we're done with setting up Slack!

Create a Github Action to notify Slack

Our next step will be somewhat similar to when we created our first Github Action. We'll create a workflow file which we'll configure to send our notifications.

While we can use our code editors to do this by creating a file in the .github directory, I'm going to use the Github UI.

First, let's navigate back to our Actions tab in our repository. Once there, select New workflow.

This time, we're going to start the workflow manually instead of using a pre-made Action. Select set up a workflow yourself at the top.

Once the new page loads, you'll be dropped in to a new template where we can start working. Here's what our new workflow will look like:

name: Slack Notifications on: pull_request: branches: [ master ] jobs: notifySlack: runs-on: ubuntu-latest steps: - name: Notify slack env: SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }} uses: abinoda/[email protected] with: args: '{\"channel\":\"[Channel ID]\",\"blocks\":[{\"type\":\"section\",\"text\":{\"type\":\"mrkdwn\",\"text\":\"*Pull Request:* ${{ github.event.pull_request.title }}\"}},{\"type\":\"section\",\"text\":{\"type\":\"mrkdwn\",\"text\":\"*Who?:* ${{ github.event.pull_request.user.login }}\n*Request State:* ${{ github.event.pull_request.state }}\"}},{\"type\":\"section\",\"text\":{\"type\":\"mrkdwn\",\"text\":\"\"}}]}' 

So what's happening in the above?

• name: we're setting a friendly name for our workflow
• on: we want our workflow to trigger when there's a pull request is created that targets our master branch
• jobs: we're creating a new job called notifySlack
• jobs.notifySlack.runs-on: we want our job to run on a basic setup of the latest Unbuntu
• jobs.notifySlack.steps: we really only have one step here - we're using a pre-existing Github Action called Slack Action and we're configuring it to publish a notification to our Slack

There are two points here we'll need to pay attention to, the env.SLACK_BOT_TOKEN and the with.args.

In order for Github to communicate with Slack, we'll need a token. This is what we're setting in env.SLACK_BOT_TOKEN. We generated this token in the first step. Now that we'll be using this in our workflow configuration, we'll need to add it as a Git Secret in our project.

The  with.args property is what we use to configure the payload to the Slack API that includes the channel ID (channel) and our actual message (blocks).

The payload in the arguments is stringified and escaped. For example, when expanded it looks like this:

{ "channel": "[Channel ID]", "blocks": [{ "type": "section", "text": { "type": "mrkdwn", "text": "*Pull Request:* ${{ github.event.pull_request.title }}" } }, { "type": "section", "text": { "type": "mrkdwn", "text": "*Who?:*n${{ github.event.pull_request.user.login }}n*State:*n${{ github.event.pull_request.state }}" } }, { "type": "section", "text": { "type": "mrkdwn", "text": "" } }] } 

Note: this is just to show what the content looks like, we need to use the original file with the stringified and escaped argument.

Back to our configuration file, the first thing we set is our channel ID. To find our channel ID, you'll need to use the Slack web interface. Once you open Slack in your browser, you want to find your channel ID in the URL:

//app.slack.com/client/[workspace ID]/[channel ID] 

With that channel ID, you can modify our workflow configuration and replace [Channel ID] with that ID:

with: args: '{\"channel\":\"C014RMKG6H2\",... 

The rest of the arguments property is how we set up our message. It includes variables from the Github event that we use to customize our message.

We won't go into tweaking that here, as what we already have will send a basic pull request message, but you can test out and build your own payload with Slack's Block Kit Builder.

Follow along with the commit!

Test out our Slack workflow

So now we have our workflow configured with our Slack app, finally we're ready to use our bot!

For this part, all we need to do is create a new pull request with any change we want. To test this out, I simply created a new branch where I added a sentence to the README.md file.

Once you create that pull request, similar to our tests workflow, Github will run our Slack workflow! You can see this running in the Actions tab just like before.

As long as you set everything up correctly, once the workflow runs, you should now have a new message in Slack from your new bot.

Note: we won't be merging that pull request in.

What else can we do?

Customize your Slack notifications

The message I put together is simple. It tells us who created the pull request and gives us a link to it.

To customize the formatting and messaging, you can use the Github Block Kit Builder to create your own.

If you'd like to include additional details like the variables I used for the pull request, you can make use of Github's available contexts. This lets you pull information about the environment and the job to customize your message.

I couldn't seem to find any sample payloads, so here's an example of a sample github context payload you would expect in the event.

Sample github context

Još Github akcija

S našom sposobnošću stvaranja novih prilagođenih tijekova rada, to nije puno što ne možemo automatizirati. Github čak ima tržnicu na kojoj možete potražiti jednu.

Ako vam se ide korak dalje, možete čak stvoriti i vlastiti! To vam omogućuje postavljanje skripti za konfiguriranje tijeka rada za izvršavanje svih zadataka koji su vam potrebni za vaš projekt.

Pridružite se razgovoru!

. @ github Akcije su sjajan način da automatizirate svoj razvojni tijek rada?

Možete raditi stvari poput automatskog pokretanja testova i slanja obavijesti na @slack! ?

Ovdje ću vas provesti kroz ono što su Akcije i kako ih možete koristiti u svom projektu

? // t.co/CNDIsNXbhm

- Colby Fayock (@colbyfayock) 3. lipnja 2020

Za što koristite Github akcije?

Podijelite sa mnom na Twitteru!

• ? Slijedite me na Twitteru
• ? Pretplatite se na moj Youtube
• Up Prijavite se za moj bilten