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

Improve Post-Processing with GitHub API Integration #121

Open
kouloumos opened this issue Jul 23, 2024 · 0 comments
Open

Improve Post-Processing with GitHub API Integration #121

kouloumos opened this issue Jul 23, 2024 · 0 comments
Assignees

Comments

@kouloumos
Copy link
Member

Part of the (optional) post-processing for transcription involves pushing output files to two GitHub repositories: bitcointranscripts and bitcointranscripts-metadata. Currently, this process requires cloning the repositories and setting their paths in a .env variable. We then change directories and execute git commands to create a new remote branch with the output files. The user/operator must then manually open a PR with the new branch.

As we move towards a hosted version of the transcription server, this process has limitations and disadvantages. To streamline the process and eliminate the need to clone repositories into the virtual server, we can use the GitHub API.

With the GitHub API, we only need an authorization token from a GitHub account. Using this token, we can create branches and commits off the main/master branch remotely, making the process more efficient and scalable.

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

No branches or pull requests

1 participant