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 access to invocation via shared or published history #18707

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Aug 15, 2024

I think this largely addresses #18695

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

@mvdbeek mvdbeek force-pushed the allow_access_to_invocation_via_shared_history branch from 2da8b62 to eca0cfb Compare August 15, 2024 11:30
@mvdbeek mvdbeek requested a review from a team August 15, 2024 14:12
@mvdbeek
Copy link
Member Author

mvdbeek commented Aug 23, 2024

Would be cool to have a review here. This is kind of important for published invocation pages.

@jmchilton jmchilton self-assigned this Aug 23, 2024
@jmchilton jmchilton merged commit 2c0a703 into galaxyproject:dev Aug 23, 2024
51 of 54 checks passed
@jmchilton
Copy link
Member

Sorry for the delay - nice work! Thank you so much.

@nsoranzo nsoranzo deleted the allow_access_to_invocation_via_shared_history branch August 30, 2024 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants