Fix/update comment

[rugeli]

Problem

What is the problem this work solves, including
#176

Solution

What I/we did to solve this problem
the workflow will on be triggered when:

1. a commit merged into main
2. a pull request has been opened/synchronized/reopened

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

Steps to Verify:

1. Push a commit on a branch that is not associated with a pull request---(the Analyze workflow will not be triggered)

[codecov-commenter]

Codecov Report

Patch and project coverage have no change.

Comparison is base (d398510) 98.42% compared to head (56afd96) 98.42%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #184   +/-   ##
=======================================
  Coverage   98.42%   98.42%           
=======================================
  Files          15       15           
  Lines         444      444           
=======================================
  Hits          437      437           
  Misses          7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mogres]

This looks great! We could also skip the entire workflow (including the analysis part) if a PR does not exist. What do you think about moving the check further up in the .yml file? This will save us storage and processing time. Or do we want to keep the results on AWS as a test?

[rugeli]

This looks great! We could also skip the entire workflow (including the analysis part) if a PR does not exist. What do you think about moving the check further up in the .yml file? This will save us storage and processing time. Or do we want to keep the results on AWS as a test?

Good suggestion! If we don't have a strong need for keeping results from non-PR commits in AWS, then I'll go for saving storage and processing time.

[meganrm]

Looks great, but I'm confused why this PR doesn't have the analyst and comment on it

[mogres]

Looks like github.event.pull_request is empty for this PR, which results in this statement evaluating to False. Maybe test it by checking what is the value stored in github.event.pull_request?

[github-actions]

Packing analysis report

Analysis for packing results located at cellpack/tests/outputs/test_spheres/spheresSST

Ingredient name	Encapsulating radius	Average number packed
ext_A	25	236.0

Packing image

Distance analysis

Expected minimum distance: 50.00
Actual minimum distance: 50.01

Ingredient key	Pairwise distance distribution
ext_A

[github-actions]

Packing analysis report

Analysis for packing results located at cellpack/tests/outputs/test_spheres/spheresSST

Ingredient name	Encapsulating radius	Average number packed
ext_A	25	236.0

Packing image

Distance analysis

Expected minimum distance: 50.00
Actual minimum distance: 50.01

Ingredient key	Pairwise distance distribution
ext_A

[mogres]

Ran the following tests:

1. Pushing a commit to a draft PR triggers the workflow
2. Pushing a commit to a non-PR branch does not trigger the workflow
3. Pushing a commit to an existing PR triggers the workflow
4. Pushing multiple commits updates the existing comment

This is expected behavior and we should be good to merge!

[meganrm]

Looks good, wait for #185 to be merged.