-
Notifications
You must be signed in to change notification settings - Fork 1
FIX: append os.Environ to docker build and docker run calls #18
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
Open
featheredtoast
wants to merge
22
commits into
main
Choose a base branch
from
add-env-to-docker-calls
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
9824c0b
FIX: append os.Environ to docker build and docker run calls
featheredtoast cadb020
DEV: apply linting
featheredtoast 7be0c18
DEV: Add linter to GH actions
featheredtoast 236bb24
DEV: gofmt
featheredtoast c9b053f
FIX: linting working directory
featheredtoast ddb30e4
FIX: working directory
featheredtoast e39e9a4
FIX: build in a temp dir
featheredtoast 1319c93
FIX: remove temp directory after build
featheredtoast b20be7e
version bump
featheredtoast 8e8e30d
DEV: Do not create subfolders in temp dirs
featheredtoast 97619a4
mkdir tmp already covers creation of working dir
featheredtoast c1763ab
DEV: gofmt
featheredtoast 81fc662
DEV: refactor names to more correct go standards
featheredtoast b98c6a9
DEV: gofmt
featheredtoast 2323a0e
FIX: ensure temp directories are created and properly cleaned up
featheredtoast cc0cfdd
DEV: rename helptext folder -> directory
featheredtoast 69f2a45
DOCS: Add note for Darwin handling for killing zombie docker processes.
featheredtoast 58bf344
DEV: prefer all context to be passed by value
featheredtoast 3410951
DEV: lint with goimports
featheredtoast d987e71
DEV: write bytes directly to output
featheredtoast 243c243
DEV: replace command with utils dockerpath
featheredtoast ab69f22
Add up, down, rm aliases
featheredtoast File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
If you are going to use sentences, it would make sense to end with punctuation.
Was this diff hunk intentional? The commit message says 'apply linting' but I don't know of any linter that would modify a string. Maybe the linter complained about the trailing full stop. If that is the case, you are only adhering to the letter of the law -- not the spirit.
This would be better:
As a user, how can I rectify the problem if I don't know what is broken? Please don't gobble error messages. We have lost entire days to developers who gobble important error messages.
The Gorbists typically style their error messages as shown in the quote above. Note that there are no sentences. (There are no capital letters and there is no full stop.) They do this because it is easier for callers to annotate the error message with additional context.
The Gorbist might say this provides satisfactory information without the clutter of a full stack trace.
https://go.dev/wiki/CodeReviewComments#error-strings