-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add link of the GitHub Issue from the License Information page #453
Comments
Yes, I think this would be helpful to the user as currently, we are only opening a new tab for discussion for the github issues as per Redirect on Successful License Submission. |
Actually, this issue can be closed as #452 intends to solve the same with some other minor changes. |
@BassCoder2808 I think it's good to solve this with #454 instead of solving it under #452 |
add link to Github issue created from license submission to list of submitted licenses at https://tools.spdx.org/app/license_requests/ @BassCoder2808 - has this been solved for and merged? |
Hi @jlovejoy actually there has been some miscommunications like there are 2 issues and 2 PRs that solve the 2 issues separately which in the end intend to do the same task. |
@BassCoder2808 - I"m confused this issue is about adding the Github link to the license info page and #452 is about removing the Standard License Header field from the output in the issue, so I think we should leave both issues? but is it that the PR #456 solves both of these issues? |
was this issue intended to add a link to the Github issue to individual license pages in the tool like https://tools.spdx.org/app/license_requests/251/ I was thinking the latter, but in any case, it is not there, so I don't think this is resolved yet |
As far as I remember @jlovejoy this was intended to open a new issues tab for that particular issue only because my thinking was that, the user will be focused on the currently submitted license only and not towards the general list |
Even though there is a link to access the request of the online tool from the Github issue, there is no link to access the GitHub issue from the online tool.
The text was updated successfully, but these errors were encountered: