# GitHub Enterprise Actions

{% embed url="<https://youtu.be/uN7ndkmgvqQ>" %}

### **Step 1:** Setting up runners

GitHub enterprise needs “self-hosted” runners to support action system calls if needed. For our actions, we need to host a Linux VM that we listen to for the jobs. To do so we need to follow these steps

* Go to settings -> Runners

<figure><img src="https://lh3.googleusercontent.com/CIBwFlRLRfAt1PcrDVQmKaZxzm_BUbIn5u-cua6qmKNviqnzAFMs6FIjG16d3YEPKFU8i6-KLyw0wIFmbKJ9I81R4fRqv5hPJfYe_Pa8Y7bpalOABkvu7XzA0epMiSqeWV-W7slgnVqNg0R-yYUTq6MjT2ftq7gXa_z_TKrltyXITN3Wykc-ba4-NQ" alt=""><figcaption></figcaption></figure>

* Click on add runner and follow the setups to connect your Linux VM with Github

<figure><img src="https://lh5.googleusercontent.com/mjv1wIHQ8l8i9LyNa78k6b_ASfVY_jMYWiryC12ETLZ2r_b2ZfN3GfirQnWR3A6e4MPufvan7sAdF51lrc1MMhbTYCplbTlx7JiRAgZFIo9Xl2r_kFmrlZpJ9C-R5ZvhVvH_NVGTMi_ZGBhKPc_ThrPA-2Tw89NAidYnMBiNis5hh1CDvlJc3w5CZQ" alt=""><figcaption></figcaption></figure>

We use these above commands in our vm like:

<figure><img src="https://lh4.googleusercontent.com/LSYl9qIl4p-go4i1HWy0jBh4V-8p4-6lyuXqxsvDdmYhMtfSH5vy7i1R9xlHdFP0lURrF5G8Ob2WCMfzespTL42wK3ml498msi0rQY6VjtHNUWsKZwHpNm8azLzc-1ubjat-g9KRW-k3q7gQeuSamk6Eaxs_QKrTDmWXBQ0rzjeM85bKpkvS-eNC0g" alt=""><figcaption></figcaption></figure>

**Note: Make sure you mkdir the same as the repo name on your GitHub. For example, here we made “ObjcTest” which is the repo name**

Check runner if connection “Idle” is available

<figure><img src="https://lh5.googleusercontent.com/rAu-OQz3rhfQoAu0ca3leyoUlGu6H5lIfTF2wE2snhnlWj8VmNsH3YZ1YQ9b4_XytEZMOtSRuB8o9YTVORc8jusE1UbULONHlT_1oWlM4uExcX06E9RMHF8CDfEDx2WWLobMKprOowOXuv8oJh95Rg5cSyvYT8KDT_af6y-aTwC9BPusTv_ANkWSbg" alt=""><figcaption></figcaption></figure>

### Step:2 Adding Repo secrets

* To add secrets (API-KEY). Settings -> Secrets -> New Repository Secrets

<figure><img src="https://lh3.googleusercontent.com/HqFLaKliyviVe-u6N20DzoXC70YFSwHsBSv3Oq-8dTTqaFCtoTd0Rl1TDUVo6iOmHbfHxigKze8P816rYCmHRxPXFwEDuHSaUPuxpcOMXOSpbtoDpnGFEiqdaaQlxyotKlLuDH9DGUtb7CKB8uJY9UHrM0cDj9GAF7zbbsE5jYVQn_Cgb64r3owSPg" alt=""><figcaption></figcaption></figure>

* For our use case we will name the secret as API\_KEY

<figure><img src="https://lh6.googleusercontent.com/pGYHx8_31qQxkJ1ZWmWylgWckZGBCWyskeP19xiTdT9RO1kfP_zjWbn1BIBjtyJWsUWTWjnKPdirtTw1NGiSYlcyrAkLdlbGcH-cozDvZjceX88xMM0mnv0hER2968EXZzlYca7NqGwM7gVDHSqpXnBqoz4E77__zuEUc9S2Cj6QTDGE3CXRtQjG0A" alt=""><figcaption></figcaption></figure>

### **Step 3:** Adding our actions.yml

* Now add our action.yml. In order to do that, make a folder structure like .github -> workflows -> action.yml, On the repo

<figure><img src="https://lh5.googleusercontent.com/EoXjsqC2mDQUSrfvQhuPxkreBGKshEvcH54xNKtCuqW_qOFiemuvRqSXnBDlhhMVjlI-zw5G_9-qyA77WRDeGDsKdfIE-Ootb6ODaAVWDSYRRjy6wZYY3d7SSzeVXQOw3feNItZzT4F5he8GD0wWyklctdnQ2Xjw1UsYU0Igi0K-hbfRPJyKkp65jg" alt=""><figcaption><p>\</p></figcaption></figure>

* Make sure that at line 18 of action.yml we have the same APP\_NAME as that of the repo name
* Commit and see the action run

<figure><img src="https://lh4.googleusercontent.com/U2rmCjJcxDTDWifIU3Vdi72hStEj4bydQEF6tpNBEs4cl4uevTRyGGpvSoJs5_slxxXRUdMPL_03c26T6PRfT_YSN7QCyWvkjDUN0J059UENH1L21-EOX6MDlPvct-jBXnwZUDj4clSuVmJ587M81_mPqEH-8Tz8dOwO4Vlii9DGGSMcF05QMoV_UQ" alt=""><figcaption></figcaption></figure>

* Once the action is done. Check our UI for the results

<figure><img src="https://lh4.googleusercontent.com/VZH7-MgT4fm5ndw64ItujSkyiM1m9CU3Or4zwTuPcBkSOkVJx_2Y_vYlwiH6VLTfGqMbDd17ROSCI75cto874o3MUU0_NMCzCAIG8UQPGPDczAJyxOizptutW0lYsN0ISniexISJ7Zk-d1pou05Ebfu9ZFqxX560hRIFE8HHaIJXMnFCNt1BU7aQzw" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh3.googleusercontent.com/6-WxaZGXVglm0FRhwFqCWaYfhtPu7GeZ23_ATQtcXDy5OvQ3MaapfxlsvQEd7As7CCciSbHs8QkPL9TGwaC5N1Jb6ftoOkeV7X08pkoNmC09Mqx30QmuDejvfMsyvr8nIBlq8_4zPyp0NGE0TxkRUy7Pak5C0pn7SwkXQnhFuNlC9FgzQRtvDlGjbA" alt=""><figcaption></figcaption></figure>