Top-level projects don't seem to work on all OS's
See original GitHub issueI’m not entirely sure if I’m reading this all right, but in our single-project repo doesn’t appear to work when running apiCheck
on linux CI while it does work on macOS locally.
Here’s a repro - https://github.com/slackhq/EitherNet/pull/52. Fails on CI with a strange check that suggests it’s expecting a subproject, but it’s a single-project repo only.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
These OSS Projects Will Be the Next Big Thing - NGINX
These OSS Projects Will Be the Next Big Thing. Dave McAllister of F5. Sr OSS Technical Evangelist for NGINX. September 27, 2022.
Read more >Barriers to Initiation of Open Source Software Projects in ...
Larger LIT organizations committed more resources to OSS projects than smaller LIT organizations, but we found no significant correlations ...
Read more >How to Contribute to Open Source
Contributing to open source happens at all levels, across projects. You don't need to overthink what exactly your first contribution will be, or...
Read more >Open Source Foundations Must Work Together to Prevent the ...
Here are a few things that OSS foundations can do to mitigate security risks: Set up an organization-wide security team to receive and...
Read more >The rise of few-maintainer projects – Increment: Open Source
Maybe this is simply because few-maintainer projects require less work, especially if our idea of what constitutes a “project” is shrinking in scope....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the report! Case sensitive may be the case here as OS X FS is case-insensitive (i.e.
Foo.txt
andfoo.txt
are considered to be the same filename), I’ll investigateSeems it wasn’t fully fixed an requires further investigation: https://github.com/Kotlin/binary-compatibility-validator/pull/79#issuecomment-1104337650