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

ci: Add issue autorespond and close workflow #526

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

rmi22186
Copy link
Member

Instructions

  1. PR target branch should be against development
  2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
  3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

  • This uses a reusable workflow to automatically comment and close issues in the android sdk.

Testing Plan

  • Was this tested locally? If not, explain why.
    Tested in a personal github repository and it works there.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

@rmi22186 rmi22186 force-pushed the ci/SQDSDKS-6972-issue-closer branch from 939958a to ed69fde Compare December 18, 2024 16:29
@rmi22186 rmi22186 merged commit 40ae360 into development Jan 7, 2025
22 of 23 checks passed
@rmi22186 rmi22186 deleted the ci/SQDSDKS-6972-issue-closer branch January 7, 2025 14:34
mparticle-automation added a commit that referenced this pull request Jan 24, 2025
## [5.58.5](v5.58.4...v5.58.5) (2025-01-24)

### Updates & Maintenance

* Add issue autorespond and close workflow ([#526](#526)) ([28ccb97](28ccb97))
* Update cross-platform-tests.yml ([#530](#530)) ([0924e88](0924e88))
* update emulator version tag ([#537](#537)) ([4f2fea6](4f2fea6))
* Update submodules ([ab53cb1](ab53cb1))
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