Skip to content

feat: adding protection email from scraping #14

feat: adding protection email from scraping

feat: adding protection email from scraping #14

Triggered via push September 21, 2024 16:44
Status Success
Total duration 1m 0s
Artifacts
Build and Test
17s
Build and Test
Deploy to GitHub Pages
25s
Deploy to GitHub Pages
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Deploy to GitHub Pages
The following actions uses node12 which is deprecated and will be forced to run on node16: JamesIves/github-pages-deploy-action@4.1.3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Deploy to GitHub Pages
The following actions use a deprecated Node.js version and will be forced to run on node20: JamesIves/github-pages-deploy-action@4.1.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deploy to GitHub Pages
Unexpected input(s) 'ACCESS_TOKEN', valid inputs are ['ssh-key', 'token', 'branch', 'folder', 'target-folder', 'commit-message', 'clean', 'clean-exclude', 'dry-run', 'git-config-name', 'git-config-email', 'repository-name', 'workspace', 'single-commit', 'silent']
Deploy to GitHub Pages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/