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

where is submid_record in the ChangeInfo #167

Open
Ai-feier opened this issue Aug 19, 2024 · 6 comments
Open

where is submid_record in the ChangeInfo #167

Ai-feier opened this issue Aug 19, 2024 · 6 comments

Comments

@Ai-feier
Copy link

image
image

@andygrunwald
Copy link
Owner

This attribute does not exist in ChangeInfo yet. See

type ChangeInfo struct {

I am happy to accept a PR that integrates this attribute.

@Ai-feier
Copy link
Author

This attribute does not exist in ChangeInfo yet. See

type ChangeInfo struct {

I am happy to accept a PR that integrates this attribute.

I'm working on the gerrit webhook development using go-gerrit, but go-gerrit has some missing fields, and currently I can implement my needs by combining ChangeInfo and EventInfo, but this method is not suitable for long-term and is not good for performance. I'd like to mention a few PRs to make go-gerrit more compatible.

@andygrunwald
Copy link
Owner

@Ai-feier Sure, go ahead.
Easy PRs that are in line with the documentation (e.g. adding new attributes) may be merged quickly.

More complicated PRs (as you mentioned some Performance topics), may benefit from an issue and a more detailed plan/design discussion before putting hours of work in.

@Ai-feier
Copy link
Author

@Ai-feier Sure, go ahead. Easy PRs that are in line with the documentation (e.g. adding new attributes) may be merged quickly.

More complicated PRs (as you mentioned some Performance topics), may benefit from an issue and a more detailed plan/design discussion before putting hours of work in.

I also want to be faster, but I'm on a business trip and need to wait until the end of work to do it

@Ai-feier Ai-feier reopened this Aug 20, 2024
@Ai-feier
Copy link
Author

@Ai-feier Sure, go ahead. Easy PRs that are in line with the documentation (e.g. adding new attributes) may be merged quickly.
More complicated PRs (as you mentioned some Performance topics), may benefit from an issue and a more detailed plan/design discussion before putting hours of work in.

I also want to be faster, but I'm on a business trip and need to wait until the end of work to do it

I also want to be faster, but I'm on a business trip and need to wait until the end of work to do it

@Ai-feier Ai-feier reopened this Aug 21, 2024
@Ai-feier
Copy link
Author

please merge the pr: #168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants