Skip to content

RTECO-1003 - added default token for github entrprise #3470

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
naveenku-jfrog merged 2 commits into from
May 5, 2026
+2 −1
Merged

RTECO-1003 - added default token for github entrprise #3470

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a1962a5
RTECO-1003 - added default token for github entrprise
naveenku-jfrog May 5, 2026
f123500
RTECO-1003 - added default token for github entrprise
naveenku-jfrog May 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .jfrog-pipelines/pipelines.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ pipelines:
description: "Git ref to checkout in jfrog/jfrog-cli (branch, tag, or SHA)."
allowCustom: true
GITHUB_DISPATCH_TOKEN:
default: ""
default: "${int_github_dispatch_token}"
description: "Token for github.jfrog.info API (repo + workflow scopes). MUST be a fine-grained PAT, a GitHub App installation token, or an OAuth App token — the JFROG org on github.jfrog.info forbids classic PATs and will return 403 with message 'forbids access via a personal access token (classic)'. If left empty, int_jfrog_cli_gh_token from the jfrog_cli_gh integration is used, and that integration itself must be configured with a fine-grained PAT (classic PATs will be rejected the same way)."
allowCustom: true
GHE_ACTIONS_RUNNER:
Expand Down
Loading