Description
Workspace
github-actions
📜 Description
Provided the correct api_base_url, host, and token for our GitHub Enterprise account, GitHub Actions is still making API requests to api.github.com instead of the configured Enterprise API base URL. This results in missing workflows and an incorrect redirect when trying to create a new workflow.
values given in the app-config.yaml
auth:
providers:
github:
development:
clientId: ${GITHUB_CLIENT_ID}
clientSecret: ${GITHUB_SECRET}
enterpriseInstanceUrl: ${GITHUTB_ENTERPRISE_URL}
Integrations:
github:
- host : ${GITHUB_HOST}
token : ${GITHUB_TOKEN}
apiBaseUrl : ${GITHUB_API_BASE_URl}
rawBaseUrl : ${GITHUB_RAW_BASE_URL}
👍 Expected behavior
GitHub Actions should respect the provided api_base_url and interact with the correct enterprise instance instead of defaulting to api.github.com.
👎 Actual Behavior
- GitHub Actions UI does not display existing workflows.
- The UI shows a "Create Workflow" button instead.
- Clicking "Create Workflow" redirects to github.com instead of the enterprise instance.
- Network inspection reveals API requests being sent to api.github.com instead of the configured Enterprise API base URL.
👟 Reproduction steps
-
Configure integration with GitHub Enterprise, providing host, token, and api_base_url.
-
Navigate to the Actions tab in the repository.
-
Observe that workflows are missing.
-
Click "Create Workflow" and note that it redirects to github.com instead of the enterprise instance.
-
Inspect network requests while interacting with Actions and see that API calls are being made to api.github.com instead of the provided api_base_url.
📃 Provide the context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
Are you willing to submit PR?
None