search

asyncapi / github-action-for-cli

GitHub Action with generator, validator, converter and others - all in one for your AsyncAPI documents with AsyncAPI CLI as backbone
Apache License 2.0
45 stars 19 forks source link

Shift the GitHub action to CLI repository #396

Open Shurtu-gal opened 2 months ago

Shurtu-gal commented 2 months ago

Why do we need this improvement?

Currently the versions, releases and other stuff are isolated from CLI which is directly coupled with this CLI. However, this creates problems in bumping of versions and keeping code updated as well.

Furthermore, any change in CLI spec could be easily made here as well.

How will this change help?

This will help in automation of releases of CLI and tie them together properly.

How could it be implemented/designed?

This issue can be resolved through the following steps:-

Additional steps:

  1. Instead of installing the asyncapi cli, dockerise the code from parent directory itself.

[!IMPORTANT] The action and bump of version would need to be tested in your personal repo or account. From my past experience would suggest using an alternate account itself.

🚧 Breaking changes

Yes

Shurtu-gal commented 2 months ago

bounty/candidate

akshatnema commented 2 months ago

@Shurtu-gal I wish to work on this issue. Basically, want to try something new, apart from website 😅

Shurtu-gal commented 2 months ago

@Shurtu-gal I wish to work on this issue. Basically, want to try something new, apart from website 😅

Great, however would need to wait for it to be accepted before assigning.

aeworxet commented 2 months ago

Bounty Issue's service comment

Text labels: bounty/2024-Q3, bounty/medium, bounty/coding First assignment to third-party contributors: 2024-06-21 00:00:00 UTC+12:00 End Of Life after: 2024-07-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.
Third-party contributors should coherently articulate how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.
Shurtu-gal commented 2 months ago

@asyncapi/bounty_team as per the rules with maintainers having more preference, I have assigned @akshatnema the issue.

akshatnema commented 2 months ago

Thanks @Shurtu-gal 😄 👍

aeworxet commented 2 months ago

Bounty Issue's Timeline

Complexity Level Assignment Date (by GitHub) Start Date (by BP Rules) End Date (by BP Rules) Draft PR Submission Final PR Merge Start Final PR Merge End
Medium 2024-06-17 2024-07-01 2024-08-11 2024-07-14 2024-07-28 2024-08-11
Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.
Keep in mind the responsibility for violations of the Timeline.
akshatnema commented 1 month ago

Hey @aeworxet, Can you please extend the deadline of bounty issue by 2 weeks, as I caught Dengue in the previous week?

aeworxet commented 1 month ago

Upon request of the Bounty Program Participant (@akshatnema), all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks.

Bounty Issue's Timeline Extended

Complexity Level Assignment Date (by GitHub) Start Date (by BP Rules) End Date (by BP Rules) Draft PR Submission Final PR Merge Start Final PR Merge End
Medium 2024-06-17 2024-07-01 2024-08-25 2024-07-28 2024-08-11 2024-08-25
Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.
Keep in mind the responsibility for violations of the Timeline.
akshatnema commented 1 month ago

Thanks @aeworxet

Shurtu-gal commented 1 month ago

@akshatnema do you need any help on this ?

aeworxet commented 2 weeks ago

@akshatnema, please provide an update to the PR.

aeworxet commented 1 week ago

@akshatnema, please provide an update to the PR.