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

DRAFT #18886

Closed
wants to merge 6 commits into from
Closed

DRAFT #18886

wants to merge 6 commits into from

Conversation

ryan-mcneil
Copy link
Contributor

WIP

Summary

  • This work is behind a feature toggle (flipper): YES/NO
  • (Summarize the changes that have been made to the platform)
  • (If bug, how to reproduce)
  • (What is the solution, why is this the solution?)
  • (Which team do you work for, does your team own the maintenance of this component?)
  • (If introducing a flipper, what is the success criteria being targeted?)

Related issue(s)

  • Link to ticket created in va.gov-team repo OR screenshot of Jira ticket if your team uses Jira
  • Link to previous change of the code/bug (if applicable)
  • Link to epic if not included in ticket

Testing done

  • New code is covered by unit tests
  • Describe what the old behavior was prior to the change
  • Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
  • If this work is behind a flipper:
    • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
    • What is the testing plan for rolling out the feature?

Screenshots

Note: Optional

What areas of the site does it impact?

(Describe what parts of the site are impacted andifcode touched other areas)

Acceptance criteria

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No error nor warning in the console.
  • Events are being sent to the appropriate logging solution
  • Documentation has been updated (link to documentation)
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Feature/bug has a monitor built into Datadog (if applicable)
  • If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
  • I added a screenshot of the developed feature

Requested Feedback

(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

@ryan-mcneil ryan-mcneil requested review from a team as code owners October 15, 2024 17:38
@ryan-mcneil ryan-mcneil changed the title Add temp failed spec + single spec in CI DRAFT Oct 15, 2024
@va-vfs-bot va-vfs-bot temporarily deployed to rm-fix-be-checks/main/main October 15, 2024 17:42 Inactive
@ryan-mcneil
Copy link
Contributor Author

I'm adding a comment with an apostrophe

@ryan-mcneil
Copy link
Contributor Author

👍

kinda shocked this worked as it was; this seems like a solid, cautious way to make it reliable, with a fallback of turning the flag off if we're wrong and things get worse.

Adding a failing comment from other PR...

@stevenjcumming
Copy link
Contributor

@ryan-mcneil can this be closed or put into a draft state?

@ryan-mcneil ryan-mcneil marked this pull request as draft October 22, 2024 15:36
@ryan-mcneil
Copy link
Contributor Author

@stevenjcumming yes, for now. When I start working on the new workflows I'll likely need to flip it to active again so that it processes correctly.

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