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

Fix: Missed SourceSpec renamings in azul.plugins.repository.canned (#2843) #3173

Merged
merged 2 commits into from
Jul 7, 2021

Conversation

amarjandu
Copy link
Contributor

@amarjandu amarjandu commented Jun 23, 2021

Author

  • PR title references issue
  • Title of main commit references issue
  • PR is linked to Zenhub issue

Author (reindex)

  • Added r tag to commit title or this PR does not require reindexing
  • Added reindex label to PR or this PR does not require reindexing

Author (freebies & chains)

  • Freebies are blocked on this PR or there are no freebies in this PR
  • Freebies are referenced in commit titles or there are no freebies in this PR
  • This PR is blocked by previous PR in the chain or this PR is not chained to another PR
  • Added chain label to the blocking PR or this PR is not chained to another PR

Author (upgrading)

  • Documented upgrading of deployments in UPGRADING.rst or this PR does not require upgrading
  • Added u tag to commit title or this PR does not require upgrading
  • Added upgrade label to PR or this PR does not require upgrading

Author (requirements, before every review)

  • Ran make requirements_update or this PR leaves requirements*.txt, common.mk and Makefile untouched
  • Added R tag to commit title or this PR leaves requirements*.txt untouched
  • Added reqs label to PR or this PR leaves requirements*.txt untouched

Author (before every review)

  • make integration_test passes in personal deployment or this PR does not touch functionality that could break the IT
  • Rebased branch on develop, squashed old fixups

Primary reviewer (after approval)

  • Commented in issue about demo expectations or labelled issue as no demo
  • Decided if PR can be labeled no sandbox
  • PR title is appropriate as title of merge commit
  • Moved ticket to Approved column
  • Assigned PR to an operator

Operator (before pushing merge the commit)

  • Checked reindex label and r commit title tag
  • Checked that demo expectations are clear or issue is labeled as no demo
  • Rebased and squashed branch
  • Sanity-checked history
  • Pushed PR branch to Github
  • Branch pushed to Gitlab or PR is labeled no sandbox
  • Build passes in sandbox and added sandbox label or PR is labeled no sandbox
  • Started reindex in sandbox or this PR does not require reindexing sandbox
  • Checked for failures in sandbox or this PR does not require reindexing sandbox
  • Added PR reference to merge commit title
  • Collected commit title tags in merge commit title
  • Moved linked issue to Merged column
  • Pushed merge commit to Github

Operator (after pushing the merge commit)

  • Moved freebies to Merged column or there are no freebies in this PR
  • Shortened the PR chain or this PR is not the base of another PR
  • Verified that N reviews labelling is accurate
  • Pushed merge commit to Gitlab or this changes can be pushed later, together with another PR
  • Deleted PR branch from Github and Gitlab

Operator (reindex)

  • Started reindex in dev or this PR does not require reindexing or does not target dev
  • Checked for failures in dev or this PR does not require reindexing or does not target dev
  • Started reindex in prod or this PR does not require reindexing or does not target prod
  • Checked for failures in prod or this PR does not require reindexing or does not target prod

Operator

  • Unassigned PR

@github-actions github-actions bot added the orange [process] Done by the Azul team label Jun 23, 2021
@codecov
Copy link

codecov bot commented Jun 23, 2021

Codecov Report

Merging #3173 (c7cff8e) into develop (c7cff8e) will not change coverage.
The diff coverage is n/a.

❗ Current head c7cff8e differs from pull request most recent head 4b1f1f8. Consider uploading reports for the commit 4b1f1f8 to get more accurate results
Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #3173   +/-   ##
========================================
  Coverage    82.68%   82.68%           
========================================
  Files          122      122           
  Lines        13552    13552           
========================================
  Hits         11206    11206           
  Misses        2346     2346           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c7cff8e...4b1f1f8. Read the comment docs.

@coveralls
Copy link

coveralls commented Jun 23, 2021

Coverage Status

Coverage remained the same at 82.925% when pulling 4b1f1f8 on issues/amar/2843-canned-spec into c7cff8e on develop.

@amarjandu
Copy link
Contributor Author

Closing this PR, branch name has the wrong issue number in it.

@dsotirho-ucsc dsotirho-ucsc removed their assignment Jun 23, 2021
@hannes-ucsc
Copy link
Member

What's a "canned repository"? I think I know what you mean but this title is confusing.

@hannes-ucsc hannes-ucsc removed their assignment Jun 24, 2021
@amarjandu amarjandu changed the title Fix: update SourceSpec usage in canned repository (#2843) Fix: update SourceSpec usage in canned staging area repository (#2843) Jun 24, 2021
@amarjandu amarjandu force-pushed the issues/amar/2843-canned-spec branch from d809c3d to 8bd0ee9 Compare June 24, 2021 18:42
@hannes-ucsc hannes-ucsc added the 1 review [process] Lead requested changes once label Jun 25, 2021
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

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

Title still not right. You're not updating a repository.

You can use file names in commit titles, you know?

@hannes-ucsc hannes-ucsc removed their assignment Jun 25, 2021
@amarjandu amarjandu force-pushed the issues/amar/2843-canned-spec branch from 8bd0ee9 to 2860fea Compare June 25, 2021 18:22
@amarjandu
Copy link
Contributor Author

amarjandu commented Jun 25, 2021

Title still not right. You're not updating a repository.

You can use file names in commit titles, you know?

Yeah, but __init__.py is not really identifiable, and I dont want use the path as the file nested pretty far. In the past other commits reference TDR plugin or DSS Plugin, going to do something similar.
Screen Shot 2021-06-25 at 11 16 49 AM

@amarjandu amarjandu changed the title Fix: update SourceSpec usage in canned staging area repository (#2843) Update SourceSpec usage in Canned plugin (#2843) Jun 25, 2021
@amarjandu amarjandu assigned amarjandu and hannes-ucsc and unassigned amarjandu Jun 25, 2021
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

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

Title even worse than before. There are no canned plugins. And "Canned" is not a proper noun either.

@hannes-ucsc hannes-ucsc removed the 1 review [process] Lead requested changes once label Jun 26, 2021
@hannes-ucsc hannes-ucsc added the 2 reviews [process] Lead requested changes twice label Jun 26, 2021
@hannes-ucsc hannes-ucsc removed their assignment Jun 26, 2021
@hannes-ucsc hannes-ucsc changed the title Update SourceSpec usage in Canned plugin (#2843) Fix: Missed SourceSpec renamings in azul.plugins.repository.canned (#2843) Jun 26, 2021
@amarjandu amarjandu force-pushed the issues/amar/2843-canned-spec branch from 2860fea to dd39f70 Compare June 29, 2021 16:47
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

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

I opened #3196 in relation to the typo you fixed.

@hannes-ucsc hannes-ucsc added no demo [process] Not to be demonstrated at the end of the sprint no sandbox [process] PR will not be tested in the sandbox labels Jul 2, 2021
@jessebrennan jessebrennan removed their assignment Jul 6, 2021
@amarjandu amarjandu force-pushed the issues/amar/2843-canned-spec branch from dd39f70 to 4b1f1f8 Compare July 7, 2021 20:58
@amarjandu amarjandu merged commit 8818635 into develop Jul 7, 2021
@amarjandu amarjandu deleted the issues/amar/2843-canned-spec branch July 7, 2021 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 reviews [process] Lead requested changes twice no demo [process] Not to be demonstrated at the end of the sprint no sandbox [process] PR will not be tested in the sandbox orange [process] Done by the Azul team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants