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

[Do not merge] Test RHTAP pipeline copy #355

Closed
wants to merge 1 commit into from

Conversation

lkolacek
Copy link
Contributor

Maintainers will complete the following section

  • Commit messages are descriptive enough
  • Code coverage from testing does not decrease and new code is covered
  • Docs updated (if applicable)
  • Docs links in the code are still valid (if docs were updated)

Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:

@lkolacek lkolacek marked this pull request as draft October 13, 2023 08:48
@lkolacek lkolacek force-pushed the STONEBLd-1685 branch 4 times, most recently from 8b911dc to 7684947 Compare October 13, 2023 09:29
Copy link
Member

@eskultety eskultety left a comment

Choose a reason for hiding this comment

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

I know this is still a draft, but I'm already seeing bits that I don't understand at all.

@@ -0,0 +1,68 @@
---
Copy link
Member

Choose a reason for hiding this comment

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

Commenting on the commit message:

Can you be more descriptive in the commit message please? It might be obvious to all current project members at the moment what exactly this Tekton template is for or at least what's the reason behind it being added, but for new members or just irregular contributors this change is completely opaque without any context. Also rember that this commit message goes to public git history, so if you don't explain anything in the commit message, in future there's going to be literally 0 trace on why some things were done in a specific way in the template, like e.g. the 'script' YAML section.

I would also like to again suggest adopting some kind of structure in the commit subjects: e.g. .tekton: <file>: <what> or similar, because that immediately will help potential reviewers identify whether that's an area they're expert on/interested in and what the gist of suggested changes is without having to go through every commit in each (or most) PR, dive into the code to understand the changes and then figure out whether they feel qualified enough to review the changes. Please take ^this just as a mere suggestion from an observer :).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK I apologize I could have added some description to commit message. This PR is not meant to be merged and it's purpose is only provide some test info. Review is not needed here and it was not requested.

- name: tag-with-latest
image: registry.access.redhat.com/ubi9/skopeo:latest@sha256:23c9ed4af1f42614bdc56309452568b2110a67f23102f42f6a6582a63b63dcdb
script: |
#!/usr/bin/env bash
Copy link
Member

Choose a reason for hiding this comment

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

Can you give a bit of trivia for this script? IOW what is it trying to test?

@lkolacek lkolacek force-pushed the STONEBLd-1685 branch 6 times, most recently from 1d773e3 to 1a42fd7 Compare October 13, 2023 09:56
@lkolacek lkolacek changed the title Test RHTAP pipeline copy [Do not merge] Test RHTAP pipeline copy Oct 13, 2023
@lkolacek lkolacek force-pushed the STONEBLd-1685 branch 17 times, most recently from d2b3eda to 57f39f1 Compare October 13, 2023 15:05
@lkolacek lkolacek force-pushed the STONEBLd-1685 branch 18 times, most recently from ab64372 to dfce975 Compare October 16, 2023 15:06
This is a debug/test PR that uses custom pipelineRun via GitHub CI - RHTAP bot
to test RHTAP specifics to support design preparation to
avoid/undo modifications in the user’s source repository

None of these changes should be merged to the main branch

STONEBLD-1685

Signed-off-by: Ladislav Kolacek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants