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

Error: slug must be lowercase alphanumeric and may contain /.-_ #142

Closed
xbreid opened this issue Mar 23, 2024 · 4 comments
Closed

Error: slug must be lowercase alphanumeric and may contain /.-_ #142

xbreid opened this issue Mar 23, 2024 · 4 comments

Comments

@xbreid
Copy link

xbreid commented Mar 23, 2024

Hello,

I was attempting to migrate to the new CI/CD workflows and noticed a bug in ariga/atlas-action/migrate/lint@v1.

The error was provided: Error: slug must be lowercase alphanumeric and may contain /.-_

From what I can gather, my dir-name unfortunately has uppercase characters, and is causing the linting action to fail.

@rotemtam
Copy link
Member

Use your dir slug , you should be able to find it in the project page, the part or the URL after atlas://

image

@xbreid
Copy link
Author

xbreid commented Mar 23, 2024

So i went into the atlas cloud UI and changed my projects slug and display name to not have a uppercase characters.

however, I am now met with the following error:

failed to push directory: Error: syncDir cannot create migration directory: active plan does not allow more than 1 migration directories

however, I can see in the UI that the CI Run pushed up this time.

@giautm
Copy link
Member

giautm commented Mar 23, 2024

Hello @xbreid, please try to rename your directory on the Settings page. Convert its name/slug to only lowercase characters and try again. If it doesn't help, please let me know with more detail (org's name /and dir's name on our Discord - giautm) - privately. So, I can help you on our side.

Screenshot 2024-03-23 at 20 31 43

@xbreid
Copy link
Author

xbreid commented Mar 23, 2024

@giautm thanks! reached out to you on Discord.

@giautm giautm closed this as completed May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants