Add githubIssueNumber field for epic work #52
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Needed to make other db changes for the project so will just include this in the main pr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As outlined in #51 this pr is to add a
githubIssueNumberto the report model to facilitate the error reporter Epic work. I chose to do the simpler change to meet the mvp, I think it would be good to make the structure more efficient in the future.When I generated the migration file it's added these
AlterFieldcommands on the auto ID fields. I think changing them fromAutoFieldtoBigAutoField? Martyn recreated this behaviour on his local version, and we agreed it looks okay.After this is merged, I don't think I'll immediately update the live version, I'll do that when code for the mvp is in place.
Fixes #51