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

CHI-3162 link to Redacted transcripts #799

Closed
wants to merge 10 commits into from

Conversation

mythilytm
Copy link
Collaborator

@mythilytm mythilytm commented Dec 18, 2024

This PR is not the cleanest or close to figuring out the solution as I mainly added logs and attempted to remove the use of docs. The issue still persists.

For the ECS task runs, my attempts to use the tl-aselo-ai-development bucket haven't panned out. It is reading the docs bucket, and even if present, not reading the transcripts directory. I need a few more hours to investigate which I won't get to until Monday.

I have changed the workflow to hardcode just development, so this PR is not fit for review or merging, just for experimentation and debugging.

Description

Checklist

  • Corresponding issue has been opened
  • New tests added
  • Feature flags / configuration added

Other Related Issues

None

Verification steps

AFTER YOU MERGE

  1. Cut a release tag using the GitHub workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
  2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
  3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

@mythilytm mythilytm closed this Jan 6, 2025
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