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

Add "next" version folder #1402

Merged
merged 2 commits into from
Nov 8, 2023
Merged

Add "next" version folder #1402

merged 2 commits into from
Nov 8, 2023

Conversation

heitortsergent
Copy link
Collaborator

Add "next" version folder so we can use it for the next k6 release.

Copy link
Member

@jdbaldry jdbaldry left a comment

Choose a reason for hiding this comment

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

LGTM assuming it's a copy-paste of v0.47.x.

Are we OK with publishing next? It's consistent with other projects but just wanted to double check.

Copy link
Member

@oleiade oleiade left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

@jdbaldry Let's assume it's okay until we're told otherwise 🤝 (@heitortsergent we should probably make it explicit in the README somehow, so that people are aware that changes made in next will be available, albeit not referenced, online)

…ectory (#1405)

* Add apply-patch script to apply changes from a commit to a second directory

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>

* Remove confusing usage output

Not implemented

---------

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
@heitortsergent heitortsergent merged commit 1b41136 into main Nov 8, 2023
6 checks passed
@heitortsergent heitortsergent deleted the next-folder branch November 8, 2023 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants