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
This issue tracks the research on ways to use fork workflow in this repository and considering whether that's desirable. An alternative is to disable some tests when secrets like EE license are missing (for outside contributors).
Currently - using pull_request - outside contributors submitting PRs will have their workflows fail due to missing secrets (e.g. EE license). Ideally, this would be resolved by work on this issue.
Acceptance criteria
A document with a list of secrets is prepared and each of them is inspected whether it would be problematic to not have access to it when using the fork workflow
Above mentioned document also contains description of day to day operations of KIC developer when using the fork workflow.
A decision is reached whether to use the fork workflow or whether to keep using the current approach (with pull_request) and disabling some tests - that require secrets - for outside contributors.
The text was updated successfully, but these errors were encountered:
Problem statement
This issue tracks the research on ways to use fork workflow in this repository and considering whether that's desirable. An alternative is to disable some tests when secrets like EE license are missing (for outside contributors).
Currently - using
pull_request
- outside contributors submitting PRs will have their workflows fail due to missing secrets (e.g. EE license). Ideally, this would be resolved by work on this issue.Acceptance criteria
pull_request
) and disabling some tests - that require secrets - for outside contributors.The text was updated successfully, but these errors were encountered: