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

feat: Execution Detail Page Link to Parent #881

Merged

Conversation

blaketastic2
Copy link
Contributor

@blaketastic2 blaketastic2 commented Jul 9, 2024

TL;DR

This PR displays the Parent execution as a link, allowing users to quickly navigate to it.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Screenshot 2024-07-09 at 12 04 51 PM

Copy link

welcome bot commented Jul 9, 2024

Thank you for opening this pull request! 🙌

These tips will help get your PR across the finish line:

  • Most of the repos have a PR template; if not, fill it out to the best of your knowledge.
  • Sign off your commits (Reference: DCO Guide).

@blaketastic2 blaketastic2 force-pushed the blake/display-parent-node-execution branch 3 times, most recently from 69b6526 to ab571a0 Compare July 9, 2024 00:50
Signed-off-by: Blake Jackson <[email protected]>
@blaketastic2 blaketastic2 force-pushed the blake/display-parent-node-execution branch from ab571a0 to 4425d74 Compare July 9, 2024 00:51
@jsonporter jsonporter merged commit b686df9 into flyteorg:master Jul 9, 2024
10 checks passed
Copy link

welcome bot commented Jul 9, 2024

Congrats on merging your first pull request! 🎉

@blaketastic2 blaketastic2 deleted the blake/display-parent-node-execution branch July 9, 2024 19:00
@flyte-bot
Copy link
Collaborator

🎉 This PR is included in version 1.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants