Pipeline specific environment variables per branch (Branch variables)

A lot of us have a branch per environment (development, stage, production).

Presently, the environment variables are set for the complete repository (Repository variables) and for the team or developer account (Team and individual account variables).

Team or individual account variables can be overridden by repository variables.

In the same order of ideas, we should consider to add the Branch variables level to offer a different environment variable values per branch (or environment).

Team or individual account variables can be overridden by repository variables, and repository variables can be overridden by branch variables.

Team/Individual > Repository > Branch.

Eg 1: Branch 1

• Team/Individual: SECRET=FOO
• Repository: SECRET=BAR
• Branch: SECRET=BAZ
• RESULT: SECRET=BAZ

Eg 2: Branch 2

• Team/Individual: SECRET=FOO
• Repository: SECRET=BAR
• Branch: SECRET is undefined
• RESULT: SECRET=BAR