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

Tracking bug of making this repository public #8

Closed
2 tasks done
kyasbal opened this issue Jan 27, 2025 · 7 comments · Fixed by #13, #9, #7, #15 or #17
Closed
2 tasks done

Tracking bug of making this repository public #8

kyasbal opened this issue Jan 27, 2025 · 7 comments · Fixed by #13, #9, #7, #15 or #17
Assignees

Comments

@kyasbal
Copy link
Member

kyasbal commented Jan 27, 2025

Please write LGTM or something on this issue if you agree that this repository is ready to be public.

Also, please link issues or PR that needs to be merged before making this public.

Blocking issues:

@kyasbal
Copy link
Member Author

kyasbal commented Jan 27, 2025

Blocked by #7

@kyasbal
Copy link
Member Author

kyasbal commented Jan 28, 2025

@RyuSA Will you make #12 blocker of this issue? Or will you do it after release?

@RyuSA
Copy link
Collaborator

RyuSA commented Jan 28, 2025

LGTM 🫶

@kyasbal kyasbal reopened this Jan 28, 2025
@kyasbal
Copy link
Member Author

kyasbal commented Jan 28, 2025

LGTM from me. I'm fine with releasing this repo as this state.

@SecretSword2
Copy link
Collaborator

LGTM 🍥

@renamoo
Copy link
Collaborator

renamoo commented Jan 28, 2025

LGTM! Not a blocker at all but I noticed a few glitches on RRADME so I opened #14

@jyane
Copy link
Collaborator

jyane commented Jan 28, 2025

+1
I found a buganizer link in the code but I guess it's fine since other our repos contain such internal bug ids / CL ids.

This was linked to pull requests Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment