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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

We should use uppercase for i in a follow up PR. 馃槈 #13861

Closed
Chumper opened this issue Jan 27, 2022 · 2 comments 路 Fixed by #14318
Closed

We should use uppercase for i in a follow up PR. 馃槈 #13861

Chumper opened this issue Jan 27, 2022 · 2 comments 路 Fixed by #14318
Assignees
Labels
good first issue Suitable for new contributors priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:refactor Refactoring or improving of existing code

Comments

@Chumper
Copy link
Contributor

Chumper commented Jan 27, 2022

@zharinov We should use uppercase for i in a follow up PR. 馃槈

 function replaceSecretsInObject(

Originally posted by @viceice in #13445 (comment)

@zharinov zharinov added the good first issue Suitable for new contributors label Jan 27, 2022
@HonkingGoose HonkingGoose added priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:ready type:refactor Refactoring or improving of existing code labels Jan 27, 2022
@MaronHatoum
Copy link
Contributor

Hi
can you please assign this issue to me?

@renovate-release
Copy link
Collaborator

馃帀 This issue has been resolved in version 31.89.7 馃帀

The release is available on:

Your semantic-release bot 馃摝馃殌

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Suitable for new contributors priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:refactor Refactoring or improving of existing code
Projects
None yet
5 participants