-
Notifications
You must be signed in to change notification settings - Fork 70
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
Implement dependent issues for GitHub Issues #1993
Comments
kylemhall
added a commit
to kylemhall/aspen-discovery
that referenced
this issue
Aug 16, 2024
We are currently using GitHub Issues for issue tracking While we are deciding on a long term issue tracker for the community ( Issues or Jira ), In the meantime it would be nice if we could use the dependent-issues action to deal with issue dependencies in the community. Once this branch is merged, setting a dependency requires only that one leave a comment on the issue in the format: Depends on Aspen-Discovery/aspen-discovery#XXXX Where XXXX is the dependent issue number. Any number of "Depends on" lines can exist in one or more comments. https://github.com/marketplace/actions/dependent-issues#dependent-issues Closes Aspen-Discovery#1993
kylemhall
added a commit
to kylemhall/aspen-discovery
that referenced
this issue
Aug 16, 2024
We are currently using GitHub Issues for issue tracking While we are deciding on a long term issue tracker for the community ( Issues or Jira ), In the meantime it would be nice if we could use the dependent-issues action to deal with issue dependencies in the community. Once this branch is merged, setting a dependency requires only that one leave a comment on the issue in the format: Depends on Aspen-Discovery/aspen-discovery#XXXX Where XXXX is the dependent issue number. Any number of "Depends on" lines can exist in one or more comments. https://github.com/marketplace/actions/dependent-issues#dependent-issues Closes Aspen-Discovery#1993
kylemhall
added a commit
to kylemhall/aspen-discovery
that referenced
this issue
Aug 16, 2024
We are currently using GitHub Issues for issue tracking While we are deciding on a long term issue tracker for the community ( Issues or Jira ), In the meantime it would be nice if we could use the dependent-issues action to deal with issue dependencies in the community. Once this branch is merged, setting a dependency requires only that one leave a comment on the issue in the format: Depends on Aspen-Discovery/aspen-discovery#XXXX Where XXXX is the dependent issue number. Any number of "Depends on" lines can exist in one or more comments. https://github.com/marketplace/actions/dependent-issues#dependent-issues Closes Aspen-Discovery#1993
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are currently using GitHub Issues for issue tracking While we
are deciding on a long term issue tracker for the community ( Issues or Jira ),
In the meantime it would be nice if we could use the dependent-issues
action to deal with issue dependencies in the community.
The text was updated successfully, but these errors were encountered: