Add generated connector repo templates and related workflows

NipunaRanasinghe commented 3 months ago

Purpose

Resolves https://github.com/ballerina-platform/ballerina-library/issues/6745.

This PR introduces the generated connector template with an scalable approach that can be extended to other library templates in the future.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information
Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

ayeshLK commented 3 months ago

@NipunaRanasinghe do we need to add library-templates/generated-connector-template/files/LICENSE ? AFAIK this would be added during the initial repo creation process.

NipunaRanasinghe commented 3 months ago

@NipunaRanasinghe do we need to add library-templates/generated-connector-template/files/LICENSE ? AFAIK this would be added during the initial repo creation process.

Yeah thats the case for our repos. But incase we need to use this workflow for the external repos (especially during the connector externalization event), better to make the license a part of the template to avoid any copyright issues in the future IMO.

So the PRs will change the license only if the target repo doesn't have it, and there will be no changes otherwise. wdyt?

NipunaRanasinghe commented 3 months ago

LGTM shall we add the standard workflows for the repo?

Yes those should also be a part of the templates. Missed to commit them. Thanks for pointing that out!

ballerina-platform / ballerina-library