You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs say to make a fork, work on it, then submit a pull request.
All such pull requests will fail automated CI testing, as there are some built-in project-level tests that require a BLN API key for testing, and forks do not have access to the environment variable / Github secret needed to pass those tests. One approach is to take a copy of the original repo; create a branch; and bring in the files from the branch for testing.
Anyone with collaborator access to this repository can use these secrets and variables for actions. They are not passed to workflows that are triggered by a pull request from a fork.
The text was updated successfully, but these errors were encountered:
The docs say to make a fork, work on it, then submit a pull request.
All such pull requests will fail automated CI testing, as there are some built-in project-level tests that require a BLN API key for testing, and forks do not have access to the environment variable / Github secret needed to pass those tests. One approach is to take a copy of the original repo; create a branch; and bring in the files from the branch for testing.
See https://github.com/biglocalnews/bln-python-client/settings/secrets/actions
Anyone with collaborator access to this repository can use these secrets and variables for actions. They are not passed to workflows that are triggered by a pull request from a fork.
The text was updated successfully, but these errors were encountered: