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

GEMNASIUM_TOKEN not being recognized in .gemnasium.yml #30

Open
monfresh opened this issue May 3, 2015 · 2 comments
Open

GEMNASIUM_TOKEN not being recognized in .gemnasium.yml #30

monfresh opened this issue May 3, 2015 · 2 comments

Comments

@monfresh
Copy link

monfresh commented May 3, 2015

Maybe I'm doing something wrong, but it seems like the command line tool is not finding GEMNASIUM_TOKEN in my .gemnasium.yml. When I run gemnasium autoupdate run, it says:

auth: You must be logged in. Please use `gemnasium auth login` first, or pass your api token with --token or GEMNASIUM_TOKEN

Do I need to pass in an option to let it know to get the values from .gemnasium.yml?

@gravis
Copy link
Member

gravis commented May 3, 2015

Hi,
Could you try to put api_key in your .gemnasium.yml file?
We kept the name for backward compatibility, and it might be confusing for new users.

Thanks

gravis pushed a commit that referenced this issue May 4, 2015
@monfresh
Copy link
Author

That worked, thanks! If possible, it would also be nice to be able to specify the GEMNASIUM_TESTSUITE variable in .gemnasium.yml. That way, I don't have to keep exporting the variable each time. I suppose I could put it in my .zshrc, but it would be preferable to have all gemnasium-related configuration in the same place. What do you think?

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

2 participants