-
Notifications
You must be signed in to change notification settings - Fork 73
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
Absolute path issue #43
Comments
@ZinatSayyad what is the path you're using for the directory of the env file? |
name: devlopment-deployment Controls when the workflow will runon: Triggers the workflow on push or pull request events but only for the dev branchpush: Allows you to run this workflow manually from the Actions tabworkflow_dispatch: A workflow run is made up of one or more jobs that can run sequentially or in paralleljobs: This workflow contains a single job called "build"build:
this is my yml file |
@AngelOnFira there are two different error I am facing ,For build that is triggered automatically when we push the code on git showing this error |
So the absolute path error should only occur if the directory environment variable starts with a slash if directory == "":
full_path = os.path.join(path, file_name)
elif directory.startswith("/"):
# Throw an error saying that absolute paths are not allowed. This is because
# we're in a Docker container, and an absolute path would lead us out of the
# mounted directory.
raise Exception("Absolute paths are not allowed. Please use a relative path.") I'm unsure why it would be failing for you, since it seems that you aren't setting that variable. Can you verify that the environment variable As for the second problem, that error is occurring because your |
I was having the same issue when I upgraded from v1.2 to v1.3.1 and was able to get it working by simply changing the ...
- name: Create .env file
uses: SpicyPizza/[email protected]
with:
...
# directory: ${{ github.workspace }}/src # <---- Worked with v1.2, but not v1.3.1
directory: src # <---- Works with v1.3.1 |
Has anyone encountered a solution for this issue? |
We might be able to do absolute paths now that we're no longer in the container. I might look back into this. |
I am facing issue while creating .env file
Traceback (most recent call last):
File "/opt/action/create-envfile.py", line 38, in
raise Exception("Absolute paths are not allowed. Please use a relative path.")
Exception: Absolute paths are not allowed. Please use a relative path. Please help to resolvee the issue @AngelOnFira
Originally posted by @ZinatSayyad in #10 (comment)
The text was updated successfully, but these errors were encountered: