Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research way(s) to use fork workflow or continue using pull_request with disabling tests requiring secrets for outside contributors #6945

Open
3 tasks
pmalek opened this issue Jan 8, 2025 · 1 comment

Comments

@pmalek
Copy link
Member

pmalek commented Jan 8, 2025

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

  • 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.
@tao12345666333
Copy link
Member

xref: #3918

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants