Skip to content
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

chore(shell): use exec to avoid spawning a grandchild process #290

Merged
merged 1 commit into from
Dec 1, 2021

Conversation

azjezz
Copy link
Owner

@azjezz azjezz commented Dec 1, 2021

Signed-off-by: azjezz azjezz@protonmail.com

@azjezz azjezz self-assigned this Dec 1, 2021
@azjezz azjezz added Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Completed Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness Type: Enhancement Most issues will probably ask for additions or changes. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity labels Dec 1, 2021
@azjezz azjezz added this to To do in v2.0.0 via automation Dec 1, 2021
@azjezz azjezz added this to the 2.0.0 milestone Dec 1, 2021
@azjezz azjezz force-pushed the chore/shell-exec branch 3 times, most recently from 82df288 to 0153af4 Compare December 1, 2021 18:19
Signed-off-by: azjezz <azjezz@protonmail.com>
@azjezz azjezz merged commit b49bd8b into 2.0.x Dec 1, 2021
v2.0.0 automation moved this from To do to Done Dec 1, 2021
@azjezz azjezz deleted the chore/shell-exec branch December 1, 2021 18:27
@coveralls
Copy link

coveralls commented Dec 1, 2021

Pull Request Test Coverage Report for Build 1527192545

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 1527133881: 0.0%
Covered Lines: 3281
Relevant Lines: 3281

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Completed Nothing further to be done with this issue. Awaiting to be closed by the requestor out of politeness Type: Enhancement Most issues will probably ask for additions or changes. Type: Maintenance Updating phrasing or wording to make things clearer or removing ambiguity
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants