Describe the bug
The CLA links in CONTRIBUTING.md point to:
https://opensource.atlassian.com/corporatehttps://opensource.atlassian.com/individual
However, these links did not open in my environment. The individual CLA link failed to resolve with the following error:
curl: (6) Could not resolve host: opensource.atlassian.com
When I opened a pull request, the CLA bot provided a different link that redirected to the current Atlassian Jira Service Management CLA form, and that flow worked correctly.
This creates confusion for new contributors because the CLA instructions in the repository do not match the signing flow provided by the CLA bot.
To Reproduce
Steps to reproduce the behavior:
Open the repository's CONTRIBUTING.md file.
Scroll to the Contributor License Agreement section.
Open the CLA for individuals or CLA for corporate contributors link.
Observe that the link may fail to resolve.
Open a pull request without having signed the CLA.
Open the CLA link provided by the CLA bot.
Observe that it redirects to the current Jira Service Management CLA portal and works correctly.
The issue can also be reproduced from the terminal with:
curl -IL https://opensource.atlassian.com/individual
Observed result:
curl: (6) Could not resolve host: opensource.atlassian.com
Expected behavior
The CLA links in CONTRIBUTING.md should direct contributors to the same current and working signing flow used by the CLA bot.
Alternatively, the documentation should clarify that contributors should use the CLA link posted by the bot after opening a pull request.
Screenshots
Environment and Version (please complete the following information):
Atlassian Plugin Version: Not applicable
Visual Studio Code Version: Not applicable
Is this a local or cloud environment?: Local
If Cloud, Browser: Not applicable
If Local, OS: macOS
Additional context
I encountered this while signing the CLA for PR #1902.
The CLA bot directed me to the following Jira Service Management form, which worked correctly:
https://atlassian-public.atlassian.net/servicedesk/customer/portal/1033/group/1043/create/1249
This may be a documentation inconsistency rather than an issue with the extension itself. Updating the links would make the contribution process clearer for first-time contributors.
Describe the bug
The CLA links in
CONTRIBUTING.mdpoint to:https://opensource.atlassian.com/corporatehttps://opensource.atlassian.com/individualHowever, these links did not open in my environment. The individual CLA link failed to resolve with the following error:
When I opened a pull request, the CLA bot provided a different link that redirected to the current Atlassian Jira Service Management CLA form, and that flow worked correctly.
This creates confusion for new contributors because the CLA instructions in the repository do not match the signing flow provided by the CLA bot.
To Reproduce
Steps to reproduce the behavior:
Open the repository's
CONTRIBUTING.mdfile.Scroll to the Contributor License Agreement section.
Open the CLA for individuals or CLA for corporate contributors link.
Observe that the link may fail to resolve.
Open a pull request without having signed the CLA.
Open the CLA link provided by the CLA bot.
Observe that it redirects to the current Jira Service Management CLA portal and works correctly.
The issue can also be reproduced from the terminal with:
Observed result:
curl: (6) Could not resolve host: opensource.atlassian.comExpected behavior
The CLA links in
CONTRIBUTING.mdshould direct contributors to the same current and working signing flow used by the CLA bot.Alternatively, the documentation should clarify that contributors should use the CLA link posted by the bot after opening a pull request.
Screenshots
Environment and Version (please complete the following information):
Atlassian Plugin Version: Not applicable
Visual Studio Code Version: Not applicable
Is this a local or cloud environment?: Local
If Cloud, Browser: Not applicable
If Local, OS: macOS
Additional context
I encountered this while signing the CLA for PR #1902.
The CLA bot directed me to the following Jira Service Management form, which worked correctly:
This may be a documentation inconsistency rather than an issue with the extension itself. Updating the links would make the contribution process clearer for first-time contributors.