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

Allow invocations from other locations than the project dir #3

Open
DiCanio opened this issue Apr 15, 2021 · 0 comments · May be fixed by #4
Open

Allow invocations from other locations than the project dir #3

DiCanio opened this issue Apr 15, 2021 · 0 comments · May be fixed by #4
Assignees
Labels
enhancement New feature or request

Comments

@DiCanio
Copy link
Member

DiCanio commented Apr 15, 2021

To use the project in its current state one needs to cd into the project directory and call the scripts.
This is kinda tedious and we should allow developers to use the scripts through symlinks and the like.

However, this is currently not possible due to the use of pwd. So, from wherever a developer will invoke any script, his current directory will be marked as the current working directory. Since there is a script that clones repositories into the current directory, this can have effects which may be undesired or even devastating.

Proposal:
Replace any usage of pwd with a routine that identifies where invoked scripts are actually located (withinin the project directory). Make use of this information throughout affected scripts to avoid any changes outside of the project directory itself.

@DiCanio DiCanio added the enhancement New feature or request label Apr 15, 2021
@DiCanio DiCanio self-assigned this Apr 15, 2021
@DiCanio DiCanio linked a pull request Apr 15, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant