Open Source FAQ

Open Source FAQ

Why was my repository rejected?

The rejection message names every failing rule at once — see the full eligibility rules and rejection-reason table. The most common one isn't a rule at all: the GitHub App was installed with "Only select repositories" and the target repo wasn't included, which shows up as zero eligible repositories rather than an explicit error. Reinstall with "All repositories," or add the repository to the App's selection.

My report disappeared — what happened?

Most likely your repository stopped passing the eligibility rules (went private, was archived, or its license changed) and the 7-day grace period ran out. See the suspend-and-restore lifecycle. Nothing was deleted — fix the underlying issue (e.g. make the repository public again) and the report comes back on its own.

Can I move a project to a different workspace?

A repository binding is tied to one workspace at a time — the same repository can't back two workspaces' plans simultaneously. Moving a project's binding to a different workspace isn't a self-serve action; contact support if you need this.

Does publishing cost anything, or expose private data?

Publishing is free and reversible — the toggle can be turned off at any time, with nothing deleted. A public report only shows what the report page itself displays (launch results, pass/fail status, timing); it doesn't expose your test case content, defects, or anything else in the project.

What if my license isn't on the approved list?

Then the repository isn't eligible for the Open Source plan — there's no manual override or appeals process. The full list is in Activating the Plan. If your project changes its license to one on the list, it becomes eligible on the next check.

Badge or banner — which should I use?

The badge is a small, shields.io-style chip — use it if you already have a row of status badges (build, license, version) at the top of your README and want to add one more. The banner is a wider, richer summary with a recent-runs trend grid — use it as its own line when you want more than a single status chip to convey. Both link to the same live report and update automatically; nothing stops you from using both.

Do I need to install a separate GitHub App for CI uploads?

No — the Qualflare GitHub App (installed while activating the plan) is only for verifying repository eligibility. Uploading test results in CI is unrelated and uses either the qualflare-action GitHub Action or the qf CLI directly with an access token; see Setting Up CI.

Related

• Activating the Plan
• Publishing a Report
• Troubleshooting Guide — general (non-OSS-specific) issues