Package Builder

Retrieve Metadata with ease to use in Package XML or SFDX commands. This tool allows you to pick which Metadata items you want to build your Package XML or Commands with view checkboxes.

Changelog

Version 1.0

Initial Release

Features Available

  • Ability to generate seleted metadata types for XML or SFDX

To install simply use the url and password below in an environment to get started.

Installation

Installation URL: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1U000006I6N9&isdtp=p1

Installation Password: 3BpmOLZnwPQO

Note: If package is installed for System Administraotrs Only the below is applicable otherwise below are not needed

After Installation

Add Tab

Now that the package is installed you will need to assign Package Builder Tab to all applicale profiles

Add Classes

Assign the below Apex Classes to a all applicable profiles.

  • MetadataService
  • MetadataSelector
  • MetadaUtility

Accessing the Tab

Pre Selection

Selection

Results

Now with the results you are able to copy and paste to your files/command prompt.

First and for most thank you for taking the time to look to contribute to Package Builder, any help is apprciated to make Package Builder better and stronger!

Code of Conduct

This project and everyone participating in it is governed by the Simplecov Material Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to github@chiefpansancolt.live.

How can I Contribute

Reporting Bugs

Before submitting a bug report

This section guides you through submitting a bug report for Package Builder. Following these guidelines helps maintainers and the community understand your report 📝, reproduce the behavior 💻 💻, and find related reports 🔎.

Before creating bug reports, please check this list as you might find out that you don’t need to create one. When you are creating a bug report, please include as many details as possible. Fill out the required template , the information it asks for helps us resolve issues faster.

Note: If you find a Closed issue that seems like it is the same thing that you’re experiencing, open a new issue and include a link to the original issue in the body of your new one.

Suggesting Enhancements

This section guides you through submitting an enhancement suggestion for Package Builder, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion 📝 and find related suggestions 🔎.

Before creating enhancement suggestions, please check this list as you might find out that you don’t need to create one. When you are creating an enhancement suggestion, please include as many details as possible. Fill in the template , including the steps that you imagine you would take if the feature you’re requesting existed.

Code Contributions

Looking to contribute to Simplecov? You can look for any tickets tagged with help-wanted

Pull Requests

The process described here has several goals:

  • Maintain Package Builder’s quality
  • Fix problems that are important to users
  • Engage the community in working toward the best possible Package Builder Interaction
  • Enable a sustainable system for Package Builder’s maintainers to review contributions

Please follow these steps to have your contribution considered by the maintainers:

  • Follow all instructions in the template
  • After you submit your pull request, verify that all status checks are passing
    What if the status checks are failing? If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.

While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.

Additional Notes

Issue and Pull Request Labels

This section lists the labels we use to help us track and manage issues and pull requests.

GitHub search makes it easy to use labels for finding groups of issues or pull requests you’re interested in. For example, you might be interested in opening an Issue or perhaps opening a pull request. To help you find issues and pull requests, each label is listed with search links for finding open items with that label in Package Builder. We encourage you to read about other search filters which will help you write more focused queries.

Type of Issue and Issue State

Label Name Description
enhancement Feature requests.
bug Confirmed bugs or reports that are very likely to be bugs.
question Questions more than bug reports or feature requests (e.g. how do I do X).
feedback General feedback more than bug reports or feature requests.
help-wanted The Package Builder team would appreciate help from the community in resolving these issues.
more-information-needed More information needs to be collected about these problems or feature requests (e.g. steps to reproduce).
needs-reproduction Likely bugs, but haven’t been reliably reproduced.
blocked Issues blocked on other issues.
duplicate Issues which are duplicates of other issues, i.e. they have been reported before.
wontfix The Package Builder team has decided not to fix these issues for now, either because they’re working as intended or for some other reason.
invalid Issues which aren’t valid (e.g. user errors).
new Tagged on Issues that are new and have not been reviewed.
tech debt Items to clean up / refactor / restructure

Pull Request Labels

Label Name Description
work-in-progress Pull Requests which are still being worked on, more changes will follow.
needs-review Pull Requests which need code review, and approval from maintainers.
under-review Pull Requests being reviewed by maintainers.
requires-changes Pull Requests which need to be updated based on review comments and then reviewed again.
needs-testing Pull Requests which need manual testing.

© Chiefpansancolt & Christopher Pezza All rights reserved.