By linking together GitHub and ActiveState, you can streamline your development and decrease the time needed to start working on your project, share your project and repo with others, or onboard new team members/employees.
If you intend on sharing your ActiveState project with others, make sure that the project is set to Public and not Private, or that those you want to share it with are already a part of your organization. Integrating your ActiveState project and your Github repo can be done at any time in your project’s development.
To link the account you will need an ActiveState project and an active Github account with a repository (repo) or branch you want to link to your project.
The following will show you how to get the most out of your ActiveState and GitHub accounts.
activestate.yamlfile into your Github repo.
Now anyone who activates that project on their machine using the
state activate <orgname>/<username> command will also pull that git repo into their project folder. One command will fetch both your repo and runtime.
Your GitHub repo will only be pulled down to your project folder on the initial activation of your project. To update your project use the
state pull command, and to update your repo use the
git pull command. Git commands will work in your activated state even if there is no Git client on your local machine, as your project will have a Git client included.
After adding the link to your GitHub repo, you can link or unlink your ActiveState account with your GitHub repository at any time. Currently a GitHub account and only be linked to one ActiveState account at a time.
To link your accounts while logged in to the Platform
Your ActiveState and GitHub accounts are now successfully linked. Checking out the project will also pull down the linked repo. Pushing and pulling changes to the repo or your project can be done using the
git push and
git pull and
state push and
state pull commands respectively.
To unlink your accounts at any time follow the steps above and click the Unlink your GitHub account. After unlinking, the GitHub account can now be linked to a different ActiveState account that has added the GitHub repo URL in the project settings.
activestate.yamlfrom your project folder into the repo.
And you’re done. Now anyone who clones that repo can activate the runtime by opening a command terminal, going to the cloned working directory, and entering
state activate to activate the runtime.
To update your project use the
state pull command and to update your repo use the
git pull command in your command terminal. Git commands will work in your activated state even if there is no Git client on your local machine, as your project will have a Git client included. Now other members of your team only need to clone the repo to begin working with the ActiveState project directly.
When creating a new Python, Perl, or Ruby project, you can directly import your project requirements from an existing GitHub repository. ActiveState will only scan the root directory for a valid requirements file and will not store ANY other data from the linked repo.
To import an existing requirements file from your GitHub repo and use it to create an ActiveState project
Your new project will now have all packages, with correct version numbers as specified in the requirements file, included prior to building.
If you received an error when scanning the repo, make sure the repo contains a valid requirements file (information on requirements files can be found here) and existing language files for the scanner to detect.
After linking your ActiveState project to an existing Github repo you can integrate your IDE with your ActiveState runtime.