You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.
I confirm that this is a issue rather than a question.
Bug report
Version
0.5.0
Steps to reproduce
Create a Gitlab repository using the example in the examples directory.
Trigger CI/CD.
What is expected?
The /public/ path to be accessible and modifiable inside of a repository.
What is actually happening?
In Gitlab, /public/ cannot be used, as statusfy will error out.
Specifically, the issue is with the part where -d public is specified to replace /dist, as Gitlab requires that the deployment folder is named public, as such, the statusfy client errors out because it cannot create the distribution files in the directory it already uses to pull the public/accessible files from.
Other relevant information
A solution could be to add a flag to specify the /public folder location, such as --public ./accessible_files.
Your OS: nodejs:latest - Gitlab CI
Node.js version: nodejs:latest - Gitlab CI
Browser version: Chrome for Android - 79.0.3945.116
Is this a global or local install? Global / Gitlab Pages
Which package manager did you use for the install? Yarn.
The text was updated successfully, but these errors were encountered:
Bug report
Version
0.5.0
Steps to reproduce
What is expected?
The
/public/
path to be accessible and modifiable inside of a repository.What is actually happening?
In Gitlab,
/public/
cannot be used, asstatusfy
will error out.Specifically, the issue is with the part where
-d public
is specified to replace/dist
, as Gitlab requires that the deployment folder is namedpublic
, as such, thestatusfy
client errors out because it cannot create the distribution files in the directory it already uses to pull the public/accessible files from.Other relevant information
A solution could be to add a flag to specify the
/public
folder location, such as--public ./accessible_files
.The text was updated successfully, but these errors were encountered: