Closed
Description
Describe the bug
When triggering the action, everything runs nominally, but ends with the error '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/'
Reproduce
Merge a pull request/push to the branch in order to trigger and run the action.
Logs
GitHub Pages Deploy Action 🚀
🚀 Getting Started Guide: https://github.com/marketplace/actions/deploy-to-github-pages
❓ FAQ/Wiki: https://github.com/JamesIves/github-pages-deploy-action/wiki
🔧 Support: https://github.com/JamesIves/github-pages-deploy-action/issues
⭐ Contribute: https://github.com/JamesIves/github-pages-deploy-action/blob/dev/CONTRIBUTING.md
📣 Maintained by James Ives (https://jamesiv.es)
Checking configuration and starting deployment… 🚦
Deploying using GitHub Token… 🔑
Configuring git…
/usr/bin/git init
Reinitialized existing Git repository in /home/runner/work/colloscope/colloscope/.git/
/usr/bin/git config user.name younesaassila
/usr/bin/git config user.email 47226184+younesaassila@users.noreply.github.com
/usr/bin/git remote rm origin
/usr/bin/git remote add origin ***github.com/younesaassila/colloscope.git
/usr/bin/git fetch --no-recurse-submodules
From https://github.com/younesaassila/colloscope
* [new branch] gh-pages -> origin/gh-pages
* [new branch] main -> origin/main
Git configured… 🔧
Starting to commit changes…
/usr/bin/git ls-remote --heads ***github.com/younesaassila/colloscope.git gh-pages | wc -l
587241942f50d21eca0758d00d23de35d8072f39 refs/heads/gh-pages
/usr/bin/git checkout --progress --force cf156f042341d5a03cb0883b53fd6a4ea759b428
Note: switching to 'cf156f042341d5a03cb0883b53fd6a4ea759b428'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at cf156f0 Update workflow
/usr/bin/git fetch ***github.com/younesaassila/colloscope.git
From https://github.com/younesaassila/colloscope
* branch HEAD -> FETCH_HEAD
/usr/bin/git worktree add --checkout github-pages-deploy-action-temp-deployment-folder origin/gh-pages
Preparing worktree (detached HEAD 5872419)
HEAD is now at 5872419 Deploying to gh-pages from @ e5d6ac0929b3e947dd2154fd2e9c9b3da13f294e 🚀
/usr/bin/rsync -q -av --checksum --progress dist/. github-pages-deploy-action-temp-deployment-folder --delete --exclude CNAME --exclude .nojekyll --exclude .ssh --exclude .git --exclude .github
/usr/bin/git status --porcelain
Running post deployment cleanup jobs… 🗑️
/usr/bin/git worktree remove github-pages-deploy-action-temp-deployment-folder --force
There is nothing to commit. Exiting early… 📭
Error: Unable to process command '::set-env name=DEPLOYMENT_STATUS::skipped' successfully.
Error: 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/
Additional Comments
No additional comment.