-
Notifications
You must be signed in to change notification settings - Fork 22
Issues: ocurrent/opam-repo-ci
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Add a way to semi-automate support for first-time package authors
growth+
#372
opened Oct 2, 2024 by
shonfeder
Add support for regexs in
x-ci-accept-failures
to ignore failures on sets of platforms
#371
opened Oct 2, 2024 by
shonfeder
Check all URLs in opam file to ensure they are live
linting
opam-ci-check
#370
opened Oct 2, 2024 by
shonfeder
Compare opam file in opam-repository against project's opam file
opam-ci-check
#374
opened Sep 6, 2024 by
punchagan
Announce opam-ci-check internally, to invite early user feedback
opam-ci-check
#377
opened Aug 7, 2024 by
shonfeder
Make the core linting logic pure and simplify the testing strategy
linting
opam-ci-check
#375
opened Jul 25, 2024 by
punchagan
Release opam-ci-check to opam repository
opam-ci-check
#376
opened Jul 25, 2024 by
punchagan
2 tasks
crashes with internal error if
capnp-secrets/
directory doesn't exist
#339
opened Jul 10, 2024 by
shonfeder
Distinguish failing CI runs from CI errors
capacity+
Work that will increase our capacity (by reducing workload or increasing our efficacy)
#328
opened Jun 26, 2024 by
shonfeder
Present CI results in diagnostic categories
UI/UX
User interface
#312
opened May 22, 2024 by
shonfeder
Add linting check for sensitive updates to existing packages
linting
#309
opened May 15, 2024 by
shonfeder
Add maintenance routine to periodically prune the job index DB
#308
opened May 15, 2024 by
shonfeder
Previous Next
ProTip!
Follow long discussions with comments:>50.