Skip to content

Conversation

@mpidcock
Copy link
Member

Link to pivotal/JIRA issue

Is PM acceptance required? (delete one)

  • Yes - don't merge until JIRA issue is accepted!

Reminder: merge main into this branch and get green tests before merging to main

What was done?

  • Removed all banners and filed a ticket to revisit the logic and tests for time-based/date dependent banners

How to test?

  • The usual way

Screenshots (for visual changes)

  • Before
image image image
  • After
image image

@github-actions
Copy link

Heroku app: https://gyr-review-app-6168-e4c6a8143b61.herokuapp.com/
View logs: heroku logs --app gyr-review-app-6168 (optionally add --tail)

Copy link
Contributor

@embarnard embarnard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seems to be some unrelated migrations wrapped up in this? Also should we just remove it instead of commenting it out

#
# Indexes
#
# index_state_file_az_intakes_email_verified (id) WHERE ((email_address IS NOT NULL) AND (email_address_verified_at IS NOT NULL))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why you're removing these or is this a mistake?

# current_sign_in_ip :string
# document_upload_notification :integer default("yes"), not null
# email :citext not null
# email_notification :integer default(0), not null
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also this, I suspect your db is out of sync

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I ran db:reset and this is what changed. I also tried db:migrate:reset, but hit an error on the first migration file that the expected table didn't exist. This is the first time I've run migrations since they were collapsed, is there another step I need to do? Are you able to run a db reset (with or without migrate)?
image

@mpidcock mpidcock force-pushed the GYR1-905-itin-filers-update branch from 4f43038 to 5188c10 Compare January 26, 2026 20:41
@mpidcock mpidcock force-pushed the GYR1-905-itin-filers-update branch from 5188c10 to 639af2d Compare January 26, 2026 20:43
Copy link
Contributor

@embarnard embarnard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@embarnard embarnard merged commit 8131834 into main Jan 26, 2026
8 checks passed
@embarnard embarnard deleted the GYR1-905-itin-filers-update branch January 26, 2026 22:10
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.

3 participants