Actions VS actions-workflow-samples

In the latest update of the Actions app, I added an “Ask ChatGPT” action to make it easy to use ChatGPT in your shortcuts.

Hey. I'm the author of the Actions app and I'm out with a new app.

Check out the "Calculate with Soulver" action in the Actions app. It makes it easy to do calculations like that. Example

Hey, I'm the creator of the Actions app. I made this app to be able to quickly send links from my iPhone to the browser on my Mac. While making it, I realized that since you can send links to your Mac that are opened there, you could send links in the form shortcuts://run-shortcut, which would run shortcuts.

Hi. I'm the creator of the Actions app. I have made a macOS app for Stable Diffusion, which lets you create images from a text description using AI. The app includes support for running the image generation directly from the Shortcuts app. iOS support is planned.

The Actions app has a "Generate CSV" action that should be faster.

This is planned

You can use the Create Symbol Image action from my Actions app.

GitHub Actions for Azure (official examples): https://github.com/Azure/actions-workflow-samples

appcontent.yml - Used to deploy my app content to the Azure App Service. Using this sample provided by Microsoft, with very minor modifications.

It's using GitHub Secrets. This guide helps: https://github.com/Azure/actions-workflow-samples/blob/master/assets/create-secrets-for-GitHub-workflows.md

For this exercise we need a personal access token from github. To ensure that the action has access to the GitHub token which you, by the way, should never expose to the public - we will place it in the secrets of the repo.

First we'll need to make some repo secrets. Here's a nice guide from Azure explaining how to do just that. It isn't difficult at all.

Add Actions secrets for the FTPS credentials. In our example the secret names are WP_USER and WP_PASSWORD.

Yep. For the projects I’ve worked on, the Azure Functions for scheduling were in their own `functions` folder at the root of the repository. Upon successful deployment of the main app, we’d then deploy the functions. Aside from that deployment happening after the main app’s, we use the same deployment configuration as the official example for GitHub Actions with Python functions: https://github.com/Azure/actions-workflow-samples/blob/master/FunctionApp/linux-python-functionapp-on-azure.yml.

We have 1 user that we use for deployment. We keep the username and password of this user in a Secret (all platforms support some form of secrets, here is some docs on Github Actions specifically).

I followed the official documentation (Link) and used the pre-defined template and it worked out of the box.