Skip to content

Conversation

@fealebenpae
Copy link
Contributor

Summary

Fix two occurrences of hardcoded paths pointing to the MEKO repository to correctly resolve the new repository name.

Proof of Work

Trivial PR.

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you checked for release_note changes?

Reminder (Please remove this when merging)

  • Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
  • Our Short Guide for PRs: Link
  • Remember the following Communication Standards - use comment prefixes for clarity:
    • blocking: Must be addressed before approval.
    • follow-up: Can be addressed in a later PR or ticket.
    • q: Clarifying question.
    • nit: Non-blocking suggestions.
    • note: Side-note, non-actionable. Example: Praise
    • --> no prefix is considered a question
@fealebenpae fealebenpae self-assigned this Apr 25, 2025
@fealebenpae fealebenpae requested a review from a team as a code owner April 25, 2025 11:49
@fealebenpae fealebenpae merged commit 9ce69d1 into master Apr 25, 2025
1 of 2 checks passed
@fealebenpae fealebenpae deleted the fealebenpae/hardcoded-repo-paths branch April 25, 2025 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants