github-actions | For internal reference | Frontend Framework library

I am new to GitHub Actions and want to build and deploy my Android app to "internal testing" at the Google Play store. I have seen some good articles on it, but have been running into the 'set-env' error. I have followed the link but still do not understand how to apply it to my specific use case.

The set-env command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Here is the error:

There seems to be some good examples without the environment files, which seems like the right way to go. I am following this, this, and this. All have some simple steps, but this is where I am having the problem:

I have 2 repos: user/ext-private and user/ext-public. I want to push some files to public repo but its failing with following error:

This question is similar to How to run a github-actions step, even if the previous step fails, while still failing the job but the accepted answer does not help me because the it creates an additional job.

What i am trying to accomplish below is

• When the test-app (step2) passes; the test-clean step should run and the github action workflow returns success.
• When the test-app (step2) fails; the test-clean, action-slack and fail-action steps should run. The github action workflow returns fails.

How do I fix the below code to make it happen?

Per the documentation found here, I have tried setting a GitHub Action environment variable but noticed that the env variables don't seem to save. Has this been deprecated or is the documentation / my implementation just incorrect?

Github Actions were working in my repository till yesterday. I didnt make any changes in .github/workflows/dev.yml file or in DockerFile.

But, suddenly in recent pushes, my Github Actions fail with the error

Setup, Build, Publish, and Deploy

...

I would like to limit concurrency to one run for my workflow:

You see a lot of articles on combining GitHub actions with Terraform. It makes sense that anytime one wants to provision something different in their infrastructure that a CI/CD pipeline would add visibility and repeatability to an otherwise manual process.

But some article make it sound as though Terraform is doing the deploying of any change. For example, this article says "anytime there is a push to the src directory it will kick off the action which will have Terraform deploy the changes made to your website."

But doesn't this only make sense if the change you are making is related to provisioning infrastructure? Why would you want any code push to trigger a Terraform job if most pushes to the codecase have nothing to do with provisioning new infrastrucutre? Aren't most code pushes things like changing some CSS on the website, or adding a function to a back-end node script. These don't require provisioning new infrastructure, as the code is just placed onto existing infrastructure.

Or perhaps the article is suggesting the repo is dedicated only to Terraform.

I built a pylint git action, for pull request, which actually works really well:

I'm trying to publish a npm package on GAR (Google Artifact Registry) through github using google-github-actions/auth@v0 and google-artifactregistry-auth

For the authentication to google from github here is what I did to use the Federation Workload Identity: