kbrashears5/github-action-file-sync

Failiures still reports action success

Closed this issue · 3 comments

I had a couple of failure cases that didn't produce a "failure" of the action. in this case, the token I used didn't have permissions to write to the target repo, but the action still reported success. In another, I had mistyped the repo name, so it couldn't pull or push into it, but it still reported success

 Repository: [icariohealth/development_standards]
Inputs
---------------------------------------------
Repositories    : icariohealth/icario-developer-portal@main
Files           : general/=developer-portal/standards/
Pull request    : false
Temp Path       : /ghafs/
---------------------------------------------
 
Intiializing git
Git initialized
 
 icariohealth/icario-developer-portal@main
  Repository name: [icariohealth/icario-developer-portal]
  Branch: [main]
  Cloning [***github.com/icariohealth/icario-developer-portal.git] to [/ghafs/icariohealth/icario-developer-portal]
  Already on 'main'
  Your branch is up to date with 'origin/main'.
  Already up to date.
   
  File: [general/=developer-portal/standards/]
  Source path: [general/]
  Source full path: [/github/workspace/general/]
  Source file name: [general]
  Destination file path: [general]
  Destination file path specified: [developer-portal/standards/]
  Copying: [/github/workspace/general/] to [/ghafs/icariohealth/icario-developer-portal/developer-portal/standards/]
  Committing changes
  [main 439da01] File sync from icariohealth/development_standards
   6 files changed, 173 insertions(+), 93 deletions(-)
   create mode 100644 developer-portal/standards/general/apis/rest_api_guidelines.md
   
  Push changes to [***github.com/icariohealth/icario-developer-portal.git]
  remote: Repository not found.
  fatal: repository 'https://github.com/icariohealth/icario-developer-portal.git/' not found
  Completed [icariohealth/icario-developer-portal]

AUTOMATICALLY GENERATED by kbrashears5/github-action-issue-notifier

Mentioning @kbrashears5 to notify them. This will be looked at soon!

This issue has not received a response in a timely manner. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.

This issue has been automatically closed. Please create a new issue if it still exists.