Skip to content
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 layout field to run model [#186530687] #622

Merged
merged 1 commit into from
Dec 3, 2023

Conversation

uraniumanchor
Copy link
Collaborator

Contributing to the Donation Tracker

  • I've added tests or modified existing tests for the change.
  • I've humanly end-to-end tested the change by running an instance of the tracker.

Issue from Pivotal Tracker

https://www.pivotaltracker.com/story/show/186530687

Description of the Change

In the interest of not making the tech_notes field an essay every time, this is the first step towards splitting out some things. The layout field is used for every single run, so it deserves its own field. It won't show up in api requests unless you ask for tech notes and have the correct permission.

Verification Process

Ran it locally, checked that the v1 api returned the field when requested, that you could edit it in the admin, etc. No complicated validation here.

@uraniumanchor uraniumanchor added this pull request to the merge queue Dec 3, 2023
Merged via the queue into master with commit 3d91ec9 Dec 3, 2023
15 checks passed
@uraniumanchor uraniumanchor deleted the 186530687-layout-field branch December 3, 2023 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant