The issue: Cannot accurately test Pull Requests from outside repositories when the Travis-CI tests require secure environment variables. Proposal: If the origin of the PR has environment variables in its Repository Settings, include those variables for the Travis-CI tests. Example: I created com…

Pass the PR origin's Repository Settings alongside Github Pull Request

native-api Split this topic March 5, 2021, 3:31pm 2

Topic		Replies	Views
Allow external pull requests to use secret variables from the forked repo Feature Requests travis-build , secret-variables	5	2096	March 5, 2021
Issue: Thoughts for Secure Environment Variables usage in PR's (Migrated from issues) Feature Requests issues-migrated	0	800	December 5, 2018
"repo:" section in travis.yml does not interpolate environment variables R travis-yml	4	602	November 11, 2020
Environment Variables are insecure and transferred to new repository owners Deployment github-integration , travis-build , bug	5	1099	May 14, 2021
Dockerhub user/password not availble in PR makes unable to check it could/not be build Travis CI Discussions & Feedback build-env	1	563	April 11, 2021