Skip to content

Rewrite - Switch to Github Actions Instead of CircleCI #359

Closed
Closed
Rewrite - Switch to Github Actions Instead of CircleCI#359
Labels
priority: highThis is an issue that should be fixed firststatus: acceptedThe issue has been accepted but still needs to be addressedtype: code changeIssue requires changes to the code basetype: dependenciesThe issue requires changes to the dependencies of the projecttype: documentationIssue requires a change to the current documentation of the codebase or producttype: infrastructureIssue involves a change to current infrastructure

Description

@JudsonStevens
JudsonStevens
opened on Jan 2, 2022

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.

Activity

  1. JudsonStevens
    added
    priority: highThis is an issue that should be fixed first
    type: dependenciesThe issue requires changes to the dependencies of the project
    feedback: discussionActive discussion is happening to scope this issue, set acceptance criteria, or decide to accept it
    type: documentationIssue requires a change to the current documentation of the codebase or product
    type: code changeIssue requires changes to the code base
    type: infrastructureIssue involves a change to current infrastructure
    status: awaiting acceptanceIssue has not been accepted - it may need documentation, discussion, or a decision - the ice box
    on Jan 2, 2022

  2. JudsonStevens commented on Jan 2, 2022

    @JudsonStevens
    JudsonStevens
    on Jan 2, 2022
    CollaboratorAuthor

    @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.

  3. aaron-junot commented on Jan 3, 2022

    @aaron-junot
    aaron-junot
    on Jan 3, 2022
    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.

  4. JudsonStevens
    added
    status: acceptedThe issue has been accepted but still needs to be addressed
    and removed
    feedback: discussionActive discussion is happening to scope this issue, set acceptance criteria, or decide to accept it
    status: awaiting acceptanceIssue has not been accepted - it may need documentation, discussion, or a decision - the ice box
    on Jan 21, 2022

  5. irvingpop commented on Jan 19, 2026

    @irvingpop
    irvingpop
    on Jan 19, 2026
    Collaborator

    fixed via #421

  6. irvingpop
    closed this as completedon Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: highThis is an issue that should be fixed firststatus: acceptedThe issue has been accepted but still needs to be addressedtype: code changeIssue requires changes to the code basetype: dependenciesThe issue requires changes to the dependencies of the projecttype: documentationIssue requires a change to the current documentation of the codebase or producttype: infrastructureIssue involves a change to current infrastructure

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions