Failing to add a galaxy role with a "documentation_url" 404 error from github api

[Alon Nisser]

I'm trying to add my first galaxy role

and I'm getting this error:

Failed to parse 'meta/main.yml'. Please refer to the 'Getting Started' documentation regarding the proper format of the 'meta/main.yml' file. Once the issue has been corrected in the repository, you can retry the import. Real Error: 404 {u'documentation_url': u'https://developer.github.com/v3', u'message': u'Not Found'} I'm checking the role for syntax error (with ansible-playbook --syntax-check option) and I don't get any error there. but yet.. something is wrong.  Any ideas to what can be the issue?  the meta file:

---

galaxy_info:

author: Alon Nisser

description: "Ansible role that nginx specifc jails for fail2ban"

# Added the following line just to check if this is the problem, it isn't   documentation_url:

company:

# If the issue tracker for your role is not on github, uncomment the

# next line and provide a value

# issue_tracker_url: http://example.com/issue/tracker

license: MIT

min_ansible_version: 1.9

#

# Below are all platforms currently available. Just uncomment

# the ones that apply to your role. If you don't see your

# platform on this list, let us know and we'll get it added!

#

platforms:

- name: Ubuntu

versions:

- saucy

- trusty

- utopic

- vivid

- name: Debian

versions:

#  - all

#  - etch

#  - jessie

#  - lenny

- squeeze

- wheezy

#

# Below are all categories currently available. Just as with

# the platforms above, uncomment those that apply to your role.

#

categories:

- monitoring

- system

dependencies: []

# List your role dependencies here, one per line.

# Be sure to remove the '[]' above if you add dependencies

# to this list.

Re-import

[Alon Nisser]

If anyone bumps into this error:

turns out that 'documentation_url' has nothing to do with the ansible meta parameter with the same name, but just a sad coincidence.. :( 

The issue is really a 404 from github api trying to find the meta/main.yml file in the expected place.

Which turns to be is in the root folder of the repo.

 Hope this would help someone else who bumps into this error