-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add Dev Container for local development #39
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #39 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 11 11
Lines 268 268
Branches 40 40
=========================================
Hits 268 268 ☔ View full report in Codecov by Sentry. |
This reverts commit ac3319d.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have much context on dev containers, but I don't see anything alarming here either.
# Download constraints | ||
curl -sSLo $CONSTRAINTS_FILE $CONSTRAINTS_URL | ||
# Remove this package from constraints | ||
sed -i "/^$(python setup.py --name)@/d" $CONSTRAINTS_FILE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed this line in colcon/ci#14 to support extensions that don't have a setup.py
. You could copy the new logic here, or just drop in colcon-clean
if you like.
This approximates colcon's CI while still streamlining development over the previous Dockerfile build setup. Also, the Dockerfile build setup (using colcon itself as the build tool) was failing to pass tests due to some file hierarchy assumptions with copyright checks using pytest, such as auto generated site files missing copyright headers.