CI Pipeline: create cassettes in fork

[waynehamadi]

Background

This is a hotfix for our current cassette workflow.
Current process:

• if prompt change
• create branch elsewhere with cassettes
• when we merge, it creates a PR that needs to be merged

New process:

• prompt changes
• create branch and create a PR whose target is the fork
• the user merges the pr to have the pipeline passing

Changes

Documentation

Test Plan

PR Quality Checklist

• My pull request is atomic and focuses on a single change.
• I have thoroughly tested my changes with multiple different prompts.
• I have considered potential risks and mitigations for my changes.
• I have documented my changes clearly and comprehensively.
• I have not snuck in any "extra" small tweaks changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)			May 17, 2023 2:44am

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (52874cc) 62.75% compared to head (ec8eebb) 62.75%.

❗ Current head ec8eebb differs from pull request most recent head a75bc71. Consider uploading reports for the commit a75bc71 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4257   +/-   ##
=======================================
  Coverage   62.75%   62.75%           
=======================================
  Files          73       73           
  Lines        3367     3367           
  Branches      487      487           
=======================================
  Hits         2113     2113           
  Misses       1107     1107           
  Partials      147      147           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[github-actions]

This PR exceeds the recommended size of 200 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size

[github-actions]

This PR exceeds the recommended size of 200 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size

[dschonholtz]

I’m gonna start being a bit more insistent about a couple things.
go through the check boxes. Think about them tick them as appropriate.
Fill in the different sections of the pr template.

What is the GitHub action you are using? This is about security so we want to make sure we aren’t exposing ourselves to a pr bot someone else owns that will exfiltrate keys or something.

You have asked for multiple reviews so don’t leave this as a draft PR. That’s confusing.

What’s the test plan. I’m assuming that the plan is to just keep putting in hot fixes until the pipeline works and cassettes run, but that is exactly that. It is an assumption

Technical debt grows and feeds on itself it is worth the time on individual PRs

[waynehamadi]

@dschonholtz alright I will do that, you have some comments about the actual change ?

[waynehamadi]

@dschonholtz oh it got merged, but here is the test plan:
now I need to create a pr to see if the cassette are created against the forks, if it doesn't work I will debug it
The github actions are pretty common for both. But only our github token is at risk and it changes at every workflow