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

GH-1909 Add validation for chef_server_url #3810

Closed
wants to merge 1 commit into from

Conversation

skmichaelson
Copy link
Contributor

No description provided.

@chef-supermarket
Copy link

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.

Non-GitHub Verified Committers

There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.

Please sign the CLA here.

@thommay
Copy link
Contributor

thommay commented Sep 15, 2015

Hi @skmichaelson, to progress further with this PR we'll need to ask you to sign a CLA.

@thommay thommay modified the milestones: Accepted Minor, Help Wanted Sep 15, 2015
@skmichaelson
Copy link
Contributor Author

@thommay, I signed the ICLA on August 20th. My Chef Supermarket profile says that I'm authorized to contribute:

supermarket

Is there something else I forgot to do?

@thommay
Copy link
Contributor

thommay commented Sep 16, 2015

Ah, the email address that you used to commit the changes isn't linked to your github account. Can you either add the email address to your github account ( https://help.github.com/articles/adding-an-email-address-to-your-github-account/ ) or follow https://help.github.com/articles/setting-your-email-in-git/ to set your email address locally; you'll then need to change your previous commits. I'd achieve this by doing a rebase and squash - https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history is a good guide to this. Thanks!

@chef-supermarket
Copy link

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

@chef-supermarket
Copy link

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.

Non-GitHub Verified Committers

There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.

GitHub Users Who Are Not Authorized To Contribute

The following GitHub users do not appear to have signed a CLA:

Please sign the CLA here.

@chef-supermarket
Copy link

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

@thommay
Copy link
Contributor

thommay commented Sep 17, 2015

👍

configurable(:chef_server_url).writes_value { |url| url.to_s.strip }
configurable(:chef_server_url).writes_value do |uri|
unless is_valid_url? uri
raise ConfigurationError, "#{url} is an invalid chef_server_url."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/url/uri/. I'll fix this on merge. 👍

@btm btm closed this in bda78d0 Nov 25, 2015
@chef chef locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants