Skip to content

Conversation

@AlamuriLokesh
Copy link
Contributor

…ormally

Copy link
Member

@artembilan artembilan left a comment

Choose a reason for hiding this comment

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

Signed-off-by: AlamuriLokesh

Please, consider to fix your Git client to provide your official name.
According to DCO, the legal obligations for contributed code has to be from official name, not nicknames.

Otherwise we cannot review and accept your change.

@AlamuriLokesh AlamuriLokesh force-pushed the feature/GH-3948 branch 2 times, most recently from 515211d to e2626ed Compare June 6, 2025 14:54
@AlamuriLokesh
Copy link
Contributor Author

Signed-off-by: AlamuriLokesh

Please, consider to fix your Git client to provide your official name. According to DCO, the legal obligations for contributed code has to be from official name, not nicknames.

Otherwise we cannot review and accept your change.

Could you please review now. I have updated my name as Alamuri Lokesh

Copy link
Contributor

@sobychacko sobychacko left a comment

Choose a reason for hiding this comment

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

Some minor comments. We need to add reference docs for this since this is a new addition.

@sobychacko
Copy link
Contributor

Merged via c491502.

@sobychacko sobychacko closed this Jul 21, 2025
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

Successfully merging this pull request may close these issues.

3 participants