GitHub Action Interview Questions | GitHub Actions Interview Questions and Answers | 18

GitHub Action Interview Questions | GitHub Actions Interview Questions and Answers | 18
Hey folks,
Welcome back to another video in the series of DevOps Interviews. This is the 18th video in this series. This is a complete 18-minute-long technical video purely on #githubactions #devops #devopsinterview etc. The difficulty level would be easy to medium level. Pick a pen and paper, and note down the questions this video covers.
LogicOps Lab - / @logicopslab
LogicOps Lab - Hindi - / @logicopslabhindi
GitHub - bit.ly/3lsUjdE
Twitter - ​ / logicopslab
Instagram - bit.ly/3tJ9Jyf
Facebook - bit.ly/3ziMoVq
Like | Share | Subscribe | Follow
github action interview questions,github actions interview questions and answers,devops real time scenarios,devops real time interviews,devops interview questions,devops interview series,devops interview questions for 3 years experience,devops interview recordings,devops interview questions and answers,github actions,interview questions on devops,interview questions on devops for freshers,github actions devops,github actions devops interview,logicopslab

[@riddhimar4810]

Thanks, it was helpful 🎉

[@LogicOpsLab]

Glad it helped!

[@amanankit6007]

What would be best answer for last question? How to customise logging for GitHub actions

[@LogicOpsLab]

To be honest, there is not a standard answer to this but for starters you can use various techniques and settings to control how information is displayed in your workflow runs. GitHub Actions uses the standard echo, printf, and other shell commands to output information, and you can also use special annotations and environment variables to modify the way logs are displayed. Several other things we can try are:
1) Log Levels
2) Use Env Variables
3) Customized annotations in the code
4) Log Formatting - You can use ANSI escape codes to format log messages with colors or other text styles. This can help differentiate between different types of log messages.
There could be more, but, this is what I have known/found.

[@durgamkhasim]

if i want to pass data b/W steps in a job it is possible how ? can please explain answer

[@karunakar2000]

Yes, it is possible to pass data between steps in a GitHub Actions job using outputs and environment variables. Using outputs in Steps -> You can set an output in one step and reference it in later steps.
Example:
yaml
Copy code
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Step 1: Generate output
id: step1
run: echo "message=Hello from Step 1" >> $GITHUB_ENV
- name: Step 2: Use the output
run: echo "Received message: ${{ env.message }}"

[@sofi6463]

The problem with your video is you didn't show anything on whiteboard please start to use a white board you don't need to come with anothe guy you can do the video alone and use a white board

[@LogicOpsLab]

Appreciate the feedback. Thanks!