Search Results for "action"

Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like. You can include the action in your workflow to trigger any event that GitHub actions supports. If the remote branch that you wish to deploy to doesn't already exist the action will create it for you. Your workflow will also need to include the actions/checkout step before this workflow runs in order for the deployment to work. ...

Checkout v7 is the official GitHub Action for checking out repository code inside a GitHub Actions workflow. It places the selected repository under the workflow workspace so build, test, lint, release, or deployment steps can access the files. By default, it fetches only one commit for the ref or SHA that triggered the workflow, but it can also fetch full branch and tag history.

This action makes it easy to quickly write a script in your workflow that uses the GitHub API and the workflow run context. To use this action, provide an input named script that contains the body of an asynchronous function call. Since the script is just a function body, these values will already be defined, so you don't have to import them.

A JupyterLab extension for version control using Git. To see the extension in action, open the example notebook included in the Binder demo. Open the Git extension from the Git tab on the left panel. This extension tries to handle credentials for HTTP(S) connections (if you don't have set up a credential manager). But not for other SSH connections. The extension can cache temporarily (by default for an hour) credentials.