-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issues for ldd-cassini are not like those for other LDDs #312
Comments
@matthewtiscareno when we first set this up, we were told that missions need their autonomy and they should not be treated the same as Discipline LDDs. That is how we treated them. We can create generic issue templates to apply to all the mission LDD repos, but they will not include the tags. Will that work here? |
Interesting. Some missions (such as ldd-vgr) are treated like the Discipline LDDs, and that was the only one I checked. Maybe it's fine this way. I'm not the steward of this LDD anyway. |
@matthewtiscareno Sorry, I am very wrong. I guess this LDD was either created before the process we instantiated or it was created incorrectly. Will update now. |
New issue template created in this repo. Disabled the tickets on the ldd-cassini repo |
Okay, great. Checking to see whether old issues are preserved, I see now that
Just checking whether all this is intended, @jordanpadams. |
This is actually expected. Pull requests are basically just a specialized Issue in GitHub system terms, so the numbers increment together.
I reopened the tickets and migrated this over to the issues repo |
Ah, that explains something we were wondering about yesterday.
Great. The former ldd-cassini issue 4 is now a redirect to (closed) PDS4-LDD-Issue-Repo issue 313. |
Hey @jordanpadams, why am I able to create an issue in this repo? For other LDDs, there isn't even an Issues tab, and instead issues are created at the PDS4-LDD-Issue-Repo where there are a bunch of tags to indicate the LDD to which the issue applies. However, at that location, there is no tag for ldd-cassini. Is this something to fix?
The text was updated successfully, but these errors were encountered: