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.

Sign up for GitHub

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

Jump to bottom

Rewrite - Switch to Github Actions Instead of CircleCI #359

Open
JudsonStevens opened this issue Jan 2, 2022 · 2 comments
Open

Rewrite - Switch to Github Actions Instead of CircleCI #359

JudsonStevens opened this issue Jan 2, 2022 · 2 comments
Labels
priority: high This is an issue that should be fixed first status: accepted The issue has been accepted but still needs to be addressed type: code change Issue requires changes to the code base type: dependencies The issue requires changes to the dependencies of the project type: documentation Issue requires a change to the current documentation of the codebase or product type: infrastructure Issue involves a change to current infrastructure

Comments

@JudsonStevens
Copy link
Collaborator

With the progress made in Github Actions over the last few years, I think it makes sense to switch over to using that instead of CircleCI. This will eliminate another third party integration and it's an easy way to keep all of the functionality under one roof. Github Actions will allow us to replicate everything the current Circle CI configuration is doing, including pushing to AWS ECR.
@JudsonStevens JudsonStevens added priority: high This is an issue that should be fixed first type: dependencies The issue requires changes to the dependencies of the project feedback: discussion Active discussion is happening to scope this issue, set acceptance criteria, or decide to accept it type: documentation Issue requires a change to the current documentation of the codebase or product type: code change Issue requires changes to the code base type: infrastructure Issue involves a change to current infrastructure status: awaiting acceptance Issue has not been accepted - it may need documentation, discussion, or a decision - the ice box labels Jan 2, 2022
@JudsonStevens
Copy link
Collaborator Author

@aaron-suarez - how do you feel about switching to Github Actions? We'll need to discuss permissions to add secrets to the Github environment as I don't believe I have that access.

@aaron-junot
Copy link
Member

I like the idea just fine. We use GitHub Actions for the front end if I'm not mistaken, so it's already a known thing around the org.

@JudsonStevens JudsonStevens added status: accepted The issue has been accepted but still needs to be addressed and removed feedback: discussion Active discussion is happening to scope this issue, set acceptance criteria, or decide to accept it status: awaiting acceptance Issue has not been accepted - it may need documentation, discussion, or a decision - the ice box labels Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: high This is an issue that should be fixed first status: accepted The issue has been accepted but still needs to be addressed type: code change Issue requires changes to the code base type: dependencies The issue requires changes to the dependencies of the project type: documentation Issue requires a change to the current documentation of the codebase or product type: infrastructure Issue involves a change to current infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aaron-junot @JudsonStevens