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.

Sign up for GitHub

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

Jump to bottom

fix: get code correctly while setting carriers [CU-34c8cxq] #65

Merged
merged 1 commit into from
Nov 2, 2022
Merged

fix: get code correctly while setting carriers [CU-34c8cxq] #65

merged 1 commit into from
Nov 2, 2022

Conversation

Alchez
Copy link
Contributor

@Alchez Alchez commented Nov 2, 2022

No description provided.

@Alchez Alchez requested a review from vjFaLk November 2, 2022 07:25
@vjFaLk
Copy link
Contributor

vjFaLk commented Nov 2, 2022

Task linked: CU-34c8cxq AttributeError: 'dict' object has no attribute 'code'

@commit-lint
Copy link

commit-lint bot commented Nov 2, 2022

Bug Fixes

  • get code correctly while setting carriers (ffe2ee0)

Contributors

Alchez

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

  • @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
  • @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
  • @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
  • @Commit-Lint merge disable will desactivate merge dependabot PR
  • @Commit-Lint review will approve dependabot PR
  • @Commit-Lint stop review will stop approve dependabot PR

@vjFaLk vjFaLk merged commit 5c6b1c4 into ParsimonyGit:master Nov 2, 2022
@Alchez Alchez deleted the fix-carrier-code branch November 2, 2022 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vjFaLk vjFaLk Awaiting requested review from vjFaLk

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Alchez @vjFaLk