We expect the Forecast Project Code to be able to refer to any valid GitHub issue number (many-to-one)
Regolith currently requires Project Codes to be unique across Forecast projects. There are currently two projects whose codes do not encode their GitHub issue number in the way that nowwhat assumes (we had previously changed these to have the same code but this broke Regolith so I changed them back).
I expect that the solution is to get Regolith to handle duplicate codes issue.
See also #32
We expect the Forecast Project Code to be able to refer to any valid GitHub issue number (many-to-one)
Regolith currently requires Project Codes to be unique across Forecast projects. There are currently two projects whose codes do not encode their GitHub issue number in the way that nowwhat assumes (we had previously changed these to have the same code but this broke Regolith so I changed them back).
I expect that the solution is to get Regolith to handle duplicate codes issue.