Feature proposal: user specific ci variables
Problem to solve
let users specify their own CI variables per repository
Further details
use case: a repository for multiple projects within same technology / account / product domain / company team (i.e. Serverless) where would be shared CI - users could successfully run only jobs where their AWS credentials have access to, other jobs would fail, however, repository's CI variables would have more weight (don't let them override everything)