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

Handles user data username case formatting #359

Merged
merged 1 commit into from
Jan 31, 2022

Conversation

PuneetPunamiya
Copy link
Member

@PuneetPunamiya PuneetPunamiya commented Jan 31, 2022

  • While running the api, config.yaml has some entries of username
    with some scopes added, which are stored in db, so there can be a
    scenario where user's username case is different than what it is
    actually on the Git application. This might loss the user's existing
    data i.e. the rating of resources which user has already given
    because it would create a new entry if username won't be found.

  • Hence this patch checks for the case of username while inserting
    the user data when user authenticates to Hub.

Signed-off-by: Puneet Punamiya [email protected]

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Run API Unit Tests, Lint Checks, API Design, Golden Files with make api-check
  • Run UI Unit Tests, Lint Checks with make ui-check
  • Commit messages follow commit message best practices

See the contribution guide for more details.

@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jan 31, 2022
  - While running the api, config.yaml has some entries of username
    with some scopes added, which are stored in db, so there can be a
    scenario where user's username case is different than what it is
    actually on the Git application. This might loss the user's existing
    data i.e. the rating of resources which user has already given
    because it would create a new entry if username won't be found.

  - Hence this patch checks for the case of username while inserting
    the user data when user authenticates to Hub.

Signed-off-by: Puneet Punamiya <[email protected]>
@tekton-robot tekton-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 31, 2022
Copy link
Member

@vinamra28 vinamra28 left a comment

Choose a reason for hiding this comment

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

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 31, 2022
@pratap0007
Copy link
Contributor

/lgtm

@sm43 sm43 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2022
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot merged commit 8ffdfdf into tektoncd:main Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants