Repository navigation
Conversation
| "errorMsg": "null", | ||
| "errorType": "message", | ||
| "url": "https://news.ycombinator.com/user?id={}", | ||
| "urlMain": "https://news.ycombinator.com/", |
There was a problem hiding this comment.
Useful to push files to another repository to be used, for example, via github
pages
inputs:
source-before-directory:
description: Source before directory from the origin directory
required: false
source-directory:
description: Source directory from the origin directory
required: true
destination-github-username:
description: Name of the destination username/organization
required: true
destination-repository-name:
description: Destination repository
required: true
user-email:
description: Email for the git commit
required: true
github-server:
description: 'Github server'
default: 'github.com'
required: false
user-name:
description: >-
[Optional] Name for the git commit. Defaults to the destination
username/organization name
required: false
default: ''
destination-repository-username:
description: '[Optional] Username/organization for the destination repository'
required: false
default: ''
target-branch:
description: >-
[Optional] set target branch name for the destination repository. Defaults
to "main"
default: main
required: false
commit-message:
description: >-
[Optional] commit message for the output repository. ORIGIN_COMMIT is
replaced by the URL@commit in the origin repo
default: Update from ORIGIN_COMMIT
required: false
target-directory:
description: '[Optional] The directory to wipe and replace in the target repository'
default: ''
required: false
create-target-branch-if-needed:
There was a problem hiding this comment.
Thanks for looking. I couldn’t find a specific change requested, as the comment text appears to be unrelated YAML from a different action. Could you clarify what you’d like changed in the HackerNews entry?
HackerNews was on the false-positive exclusions list. The old entry
scraped the HTML profile page for "No such user." / "Sorry.", which is
fragile and produced false positives.
This switches detection to the public Firebase API:
user returns a numeric timestamp, so a username can't collide with
the match string)
Validation: