Skip to content

Add 0$ transaction message to google sheet requests - #4018

Open
annagav wants to merge 1 commit into
mainfrom
ag/add_google_refunds_message
Open

annagav wants to merge 1 commit into
mainfrom
ag/add_google_refunds_message

Conversation

@annagav

@annagav annagav commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

What are the relevant tickets?

N/A

Description (What does it do?)

If the transaction is a 0$ transaction add that to the messaging in the Refunds spreadsheet.

How can this be tested?

This is hard to test. Just make sure that it looks reasonable and doesn't break anything.

@github-actions

Copy link
Copy Markdown

OpenAPI Changes

Show/hide changes
## Changes for v0.yaml:
5 changes: 4 error, 0 warning, 1 info
error	[response-required-property-removed] at head/openapi/specs/v0.yaml
	in API GET /api/v2/pages/?fields=*&type=cms.coursepage
		removed the required property `items/items/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v0.yaml
	in API GET /api/v2/pages/?fields=*&type=cms.programpage
		removed the required property `items/items/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v0.yaml
	in API GET /api/v2/pages/{id}/
		removed the required property `oneOf[#/components/schemas/CoursePageItem]/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v0.yaml
	in API GET /api/v2/pages/{id}/
		removed the required property `oneOf[#/components/schemas/ProgramPageItem]/testimonials` from the response with the `200` status

info	[api-schema-removed]
	in components/schemas
		removed the schema `TestimonialItem`



## Changes for v1.yaml:
5 changes: 4 error, 0 warning, 1 info
error	[response-required-property-removed] at head/openapi/specs/v1.yaml
	in API GET /api/v2/pages/?fields=*&type=cms.coursepage
		removed the required property `items/items/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v1.yaml
	in API GET /api/v2/pages/?fields=*&type=cms.programpage
		removed the required property `items/items/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v1.yaml
	in API GET /api/v2/pages/{id}/
		removed the required property `oneOf[#/components/schemas/CoursePageItem]/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v1.yaml
	in API GET /api/v2/pages/{id}/
		removed the required property `oneOf[#/components/schemas/ProgramPageItem]/testimonials` from the response with the `200` status

info	[api-schema-removed]
	in components/schemas
		removed the schema `TestimonialItem`



## Changes for v2.yaml:
5 changes: 4 error, 0 warning, 1 info
error	[response-required-property-removed] at head/openapi/specs/v2.yaml
	in API GET /api/v2/pages/?fields=*&type=cms.coursepage
		removed the required property `items/items/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v2.yaml
	in API GET /api/v2/pages/?fields=*&type=cms.programpage
		removed the required property `items/items/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v2.yaml
	in API GET /api/v2/pages/{id}/
		removed the required property `oneOf[#/components/schemas/CoursePageItem]/testimonials` from the response with the `200` status

error	[response-required-property-removed] at head/openapi/specs/v2.yaml
	in API GET /api/v2/pages/{id}/
		removed the required property `oneOf[#/components/schemas/ProgramPageItem]/testimonials` from the response with the `200` status

info	[api-schema-removed]
	in components/schemas
		removed the schema `TestimonialItem`



Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant