opened
DemonixCraft-1
username_0
I changed a few things in installalliases and moved some commands around in install.sh. Now I completely understand if you don't want to do this, due to Travis CI being for larger projects, and I'll gladly make a commit with the same changes but remove CI Integration. Here it is, `.travis.yml`, the config file for Travis CI, who in which will help us test, build, and deploy our commits with ease. I am unsure whether the owner of the repo will have to manually integrate Travis CI for this to work. My config demands that the test project is build in a Google Compute Engine using the Windows Operating System with a mere 3 environment variables (because these environment variables were defined in my fork, they may need to be redefined in every fork) : 

* USER_NAME : Username of the commiter

* USER_EMAIL : Email of the commiter


**Deploy Variables : ** (NOTE : These can be removed if the owner of the repo feels uncomfortable doing this)

* GITHUB_TOKEN : Personal Access Token of the Repo Owner with the following scopes : repo, read:org, write:repo_hook, and user:email. This token is not shown in script, as it can be secretly passed to Travis as a secure variable. Again, I can remove the entire deploy section if you don't want to do this.

The goal of this PR is to make testing the win-sudo repo easier, as Travis CI builds the project in an isolated computer and will check for any errors. Since Travis CI works with Linux Distros, I had to move a few things around to installation would work both in Linux and Bash. 

If username_1 doesn't want to go through with the `deploy` part I can just set the functionality to just check if the file works properly.
Integrated Travis CI + Minor Changes
issue
created
imachug
username_1
Sorry for inactivity.
comment