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.

Sign up for GitHub

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

Jump to bottom

Release first to AutomtionHub, then to Galaxy #1054

Open
andy-maier opened this issue Jul 19, 2024 · 0 comments
Open

Release first to AutomtionHub, then to Galaxy #1054

andy-maier opened this issue Jul 19, 2024 · 0 comments
Assignees
@andy-maier
Labels
area: setup type: feature
Milestone
1.10.0

Comments

@andy-maier
Copy link
Member

Since the collection import on AutomationHub is more restrictive than on Galaxy, we should import first to AutomtionHub, then to Galaxy when we make a release.

See also issue #530 for command driven import to AutomationHub.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andy-maier andy-maier

Labels
area: setup type: feature
Projects
None yet
Milestone
1.10.0
Development

No branches or pull requests
1 participant
@andy-maier