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

Switch metapackage example from cpu-z to autohotkey, which is community maintained. #70

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

kilobyte1024
Copy link

@kilobyte1024 kilobyte1024 commented Jul 24, 2024

Description Of Changes

Switch metapackage example from cpu-z to autohotkey, which is community maintained.

  • YOUR GIT COMMIT MESSAGE FORMAT IS EXTREMELY IMPORTANT. We have a very defined expectation for this format and are sticklers about it. Really, READ the entire Contributing document. It will save you and us pain.

There is no CONTRIB*.md document in this repo. I found a CONTRIB file in another choco community repo nearby and it didn't mention anything about git commit message formatting. So I am going with my own random commit message & eagerly awaiting pushback.

I will send a separate PR to update autohotkey to use this format. Originally I was going to use 7zip but it is too complicated to use for an example. For now, updating to a community-maintained package still provides value because it allows these types of edits, updates to Chocolatey-AU, etc.

Motivation and Context

Having community maintained packages as examples,

Testing

Operating Systems Testing

None - N/A

Change Types Made

  • n/a Bug fix (non-breaking change).
  • n/a Feature / Enhancement (non-breaking change).
  • n/a Breaking change (fix or feature that could cause existing functionality to change).
  • Documentation changes.
  • n/a PowerShell code changes.

Change Checklist

  • Requires a change to the documentation.
  • Documentation has been updated.
  • n/a Tests to cover my changes, have been added.
  • n/a All new and existing tests passed?
  • n/a PowerShell code changes: PowerShell v2 compatibility checked?

Related Issue

Fixes #69

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.

1 participant