-
Notifications
You must be signed in to change notification settings - Fork 113
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
chore: added credentials to javascript transformations #3408
chore: added credentials to javascript transformations #3408
Conversation
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3408/test-report.html |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3408 +/- ##
===========================================
- Coverage 88.06% 88.05% -0.02%
===========================================
Files 577 577
Lines 31148 31164 +16
Branches 7428 7430 +2
===========================================
+ Hits 27431 27440 +9
- Misses 3379 3414 +35
+ Partials 338 310 -28 ☔ View full report in Codecov by Sentry. |
Small nit, given your branch is |
This branch name is auto generated from linear to link the github PRs to linear tasks. Lets see if we can do something about it. |
Quality Gate passedIssues Measures |
What are the changes introduced in this PR?
Added credentials to javascript transformations
What is the related Linear task?
Resolves INT-XXX
Please explain the objectives of your changes below
Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here
Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?
N/A
Any new dependencies introduced with this change?
N/A
Any new generic utility introduced or modified. Please explain the changes.
N/A
Any technical or performance related pointers to consider with the change?
N/A
@coderabbitai review
Developer checklist
My code follows the style guidelines of this project
No breaking changes are being introduced.
All related docs linked with the PR?
All changes manually tested?
Any documentation changes needed with this change?
Is the PR limited to 10 file changes?
Is the PR limited to one linear task?
Are relevant unit and component test-cases added?
Reviewer checklist
Is the type of change in the PR title appropriate as per the changes?
Verified that there are no credentials or confidential data exposed with the changes.