feedback
feedback copied to clipboard
A place to discuss feedback about the pull request and web product experience.
I'm formally logging here as a bug since the API not returning accurate data is not expected. (the support email thread got logged in the below discussion item, but I...
### Thanks for dropping by! 👋 We've been working on improving the repo configuration and set up.. - How was your experience setting up your repo? - Did you experience...
**Describe the bug** PRs from external contributors fail CI. > The PR is happening in a forked repo. Using tokenless upload. > Tokenless has reached GitHub rate limit. **Environment (please...
**Describe the bug** Codecov not reporting back to Github Pull Request checks, even though report is successfully uploaded. Checks always remain in "Expected" state. **Environment (please complete the following information):**...
**Describe the bug** I have configured self-hosted codecov and Github app according to [Self-Hosted Install Guide](https://docs.codecov.com/docs/installing-codecov-self-hosted). The app has appropriate permissions and the PEM file is accessible inside the docker...
Requesting notification and messaging to alert org admins that they “are _going_ to hit the seat limit”. Maybe an option to toggle this alert on/off, and the ability to set...
### Thanks for dropping by! 👋 We'd love your feedback about the bundle analysis configuration and tool generally.. - How was your experience setting up bundle analysis in your repo?...
**Describe the bug** ```yaml ignore: - !Sources/ ``` in `codecov.yml` produces: ``` yaml.constructor.ConstructorError: could not determine a constructor for the tag '!Sources/' in "", line 2, column 5: - !Sources/...
**Describe the bug** I've configured the project and patch status checks to be informational: ```yml coverage: status: project: informational: true patch: informational: true ``` The documentation on https://docs.codecov.com/docs/commit-status states that...
**What product do you want to improve?** YAML **Is your feature request related to a problem? Please describe.** Sometimes it's easier to say which paths should be _in_-cluded rather than...