{"id":19292147,"url":"https://github.com/nasa-pds/pds4-context-products","last_synced_at":"2026-03-01T18:01:21.161Z","repository":{"id":257758012,"uuid":"859229851","full_name":"NASA-PDS/pds4-context-products","owner":"NASA-PDS","description":"Repository for managing PDS4 Context Products","archived":false,"fork":false,"pushed_at":"2026-02-18T22:02:05.000Z","size":94516,"stargazers_count":1,"open_issues_count":7,"forks_count":4,"subscribers_count":5,"default_branch":"main","last_synced_at":"2026-02-19T03:57:46.444Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/NASA-PDS.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2024-09-18T10:03:37.000Z","updated_at":"2026-02-12T23:53:52.000Z","dependencies_parsed_at":null,"dependency_job_id":"63248d55-7c18-46df-b1ba-007d489ea3f7","html_url":"https://github.com/NASA-PDS/pds4-context-products","commit_stats":null,"previous_names":["nasa-pds/pds4-context-products"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/NASA-PDS/pds4-context-products","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Fpds4-context-products","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Fpds4-context-products/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Fpds4-context-products/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Fpds4-context-products/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/NASA-PDS","download_url":"https://codeload.github.com/NASA-PDS/pds4-context-products/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Fpds4-context-products/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29977966,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-01T16:35:47.903Z","status":"ssl_error","status_checked_at":"2026-03-01T16:35:44.899Z","response_time":124,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-09T22:29:26.894Z","updated_at":"2026-03-01T18:01:21.143Z","avatar_url":"https://github.com/NASA-PDS.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# PDS4 Context Product Management\nThis repository is for managing the **latest versions** of all PDS4 Context Products across NASA and IPDA archives. It is also the primary conduit for submitting updates to existing context objects, proposing new context objects, and filing issues on existing context objects.\n\n- [Overview](#overview)\n- [Raising Issues](#raising-issues)\n- [Contributing Updates and New Products](#contributing-updates-and-new-products)\n  - [To Request a New or Updated Context Product](#to-request-a-new-or-updated-context-product)\n  - [To Create a New Context Product](#to-create-a-new-context-product)\n  - [To Update an Existing Context Product](#to-update-an-existing-context-product)\n- [Governance](#governance)\n  - [Investigation LID Prefix](#investigation-lid-prefix)\n  - [Instrument Host LID Prefix](#instrument-host-lid-prefix)\n  - [Instrument LID Prefix](#instrument-lid-prefix)\n- [Using GitHub Tools to Create and Update Products](#using-github-tools-to-create-and-update-products)\n\n## Overview\n At the IPDA Steering Committee meeting of September 2024, a need was identified for more transparency and better communication regarding the context products that are being created and used across PDS4-based systems in order to avoid duplication and to encourage best practices and collaboration. This repository was established in response to that finding.\n\n**This repository contains only the latest version of each context product. The full, official archive, containing all versions, is curated by the PDS Engineering Node at https://pds.nasa.gov/data/pds4/context-pds4/.**\n\n## Raising Issues\n\nAny GitHub user can raise an issue in this repo. \n\nCommon reasons for raising issues include:\n- To request a new context product be created\n- To request a modification to the content of an existing context product\n- To report a problem noted in an existing context product\n\nFor tracking purposes, you should raise an issue even if you plan to do the work yourself. This helps \nensure that development is visible to others who might be interested.\nDiscussion and collaboration on proposed additions and changes happens in the comment thread associated \nwith each issue. \n\n## Contributing Updates and New Products\n\nIf you are planning to make modifications or submit a new context product yourself, here's the workflow:\n1. Raise an issue in the NASA-PDS repo if one does not already exist.\n2. Fork the NASA-PDS repo into your own GitHub account space to create a working copy.\n3. In your working copy of the repo, create a branch with a name that contains the issue \nnumber(s) of the related issue(s)\n4. Edit the files in the new branch of your working repo.\n5. When you're done, file a Pull Request (PR) in the \n[NASA-PDS4/pds4-context-products](https://github.com/NASA-PDS/pds4-context-products/pulls) \nrepo to request that EN merge the \nbranch from your working copy into the NASA-PDS repo.\n\nEN will take it from there.\n\nDetails of each step, including information on using the GitHub text editor, the GitHub \nDesktop app, and the git Command Line Interface (CLI) to make and publish changes, are \nprovided in [Using GitHub Tools to Create and Update Products](#using-github-tools-to-create-and-update-products), below.\n\n### To Request a New or Updated Context Product\nWhen you need a new context product, or need updates to an existing context product: \n1. Create an issue in the NASA-PDS repository requesting the addition/change. \nHere's a handy link directly to the right \"New issue\" button: [New issue](https://github.com/NASA-PDS/pds4-context-products/issues/new/choose). \n2. Select \"New Context Product Request\" for a new product or \"Update Context Product Request\" \nfor a modification, and fill in the form that pops up. \n   - Do check before raising the issue that someone else hasn't \n   already made the same request by looking over the \n   [the current issues list](https://github.com/NASA-PDS/pds4-context-products/issues).\n   - Include whatever details you have. If you've already got a draft XML file, but are not \n   planning to contribute to the repo by making the modifications yourself, you can paste the\n   content of the XML file here and EN personnel will take care of it.\n3. Click the green \"Create\" button in the lower right corner of the form to submit the \nrequest.\n4. If you expect discussion, or want to get an email notice if someone comments, go back to \n[the current issues list](https://github.com/NASA-PDS/pds4-context-products/issues) and\nclick on the title of the issue you just created. At the bottom of the right column, there\nis a \"Subscribe\" button. Click it to subscribe or unsubscribe from notifications.\n\nIf you are not planning to create or update the context product yourself, you're done (though \nyou may be contacted to answer questions or review the product someone else creates for you). \nIf you *are* planning to create/update the product yourself, read on.  \n\n### To Create a New Context Product\n\nYou will need to consult the [Guide to PDS4 Context Products](https://pds.nasa.gov/datastandards/documents/context/PDS4_Context_Products_Guide.v3.pdf) for \nlogical identifier (LID) formation rules and the related file naming conventions. These \nvary slightly depending on the type of the context product you're creating. Inspecting\na few existing context products of the same type should help to clarify the instructions.\nPay particular attention to ```\u003ctype\u003e``` fields, which are often incorporated into file \nnames.\n\nFor both LIDs and filenames, make a reasonable guess and prpose them in the issue you\ncreate. If you need a quick review, tag Richard Chen (@rchenatjpl) to ask for one. ***EN \npersonnel will adjust the LIDs and filenames if needed***, so checking with EN early on \nthis point can save the effort of having to change these parameters in any data products you \nmight be creating while the new context products are being reviewed. \n\nThe items you need to address to create a new context product are:\n- Determine the type of the context product you will create. If in doubt, ask Richard Chen \n(@rchenatjpl) in the issue comments.\n- Determine the LID and filename you will use to submit the new product.\n- Make sure the file name ends in \"_v1.0\", with a file extension of \".xml\".\n- Create the new context product in the corresponding context type folder (a new instrument \ngoes in the *context-pds4/instrument* folder, a new mission goes in the *context-pds4/\ninvestigation* folder, etc.) of your own working branch. \nMake sure to use the full file name with the version number and extension. \n- Follow the [Guide to PDS4 Context Products](https://pds.nasa.gov/datastandards/documents/context/PDS4_Context_Products_Guide.v3.pdf) \nfor including associations and other aspects of content specific to the context type. \n- Validate the context product using the *Validate Tool*, if possible.\n\nYou only need to focus on creating the context product itself. EN will handle the updates\nrequired to collection inventory files and labels when they resolve your pull request.\n\nDetails for working in GitHub to make these changes are covered in [Using GitHub Tools to Create and Update Products](#using-github-tools-to-create-and-update-products), below.\n\n### To Update an Existing Context Product\n\nYou must not change either the logical identifier (LID) or file name root when updating an \nexisting context product. Depending on the updates needed, you may need to consult the\n[Guide to PDS4 Context Products](https://pds.nasa.gov/datastandards/documents/context/PDS4_Context_Products_Guide.v3.pdf) for content details.\n\nWhen updating an existing Context Product, follow these steps:\n- Locate the current version of the product in the *context-pds4* type folder (an instrument \nwill be in the *context-pds4/instrument* folder, a mission will be in the *context-pds4/\ninvestigation* folder, etc.) of your own working branch.\n- Rename the existing file ***only*** to increment the version number at the end of the file name. \nIncrement the minor version for a minor change, the major version for a major change.\n- Edit the renamed file. The first changes you should make are:\n  - Increment the ```\u003cversion_id\u003e``` to match the version in the file name.\n  - Add a new ```\u003cModification_Detail\u003e``` to the ```\u003cModification_History\u003e``` to document\n  the changes being made.\n- Make whatever additional changes are needed.\n- Save the file.  \n\nYou only need to focus on updating the context product itself. EN will handle the updates\nrequired to collection inventory files and labels when they resolve your pull request.\n\nDetails for working in GitHub to make these changes are covered in [Using GitHub Tools to Create and Update Products](#using-github-tools-to-create-and-update-products), below.\n\n## Governance\nWith most context products originating from a parent investigation, the lead agency of an investigation governs over the context products that fall under that investigation. Creation and management of context products related to an investigation can be delegated to other affilliated agencies through collaboration and discussion.\n\nFor context products that do not originate from an investigation (e.g., a target context product), the agency who identifies and creates the context product will gain ownership over that context product.\n\n### Investigation LID Prefix\nLID prefix for the lead agency. If there is not a clear lead agency, then this is determined via discussion amongst the affiliated agencies.\n\n### Instrument Host LID Prefix\nLID prefix for the Instrument Host lead agency. If there is not a clear lead agency, then this is determined via discussion amongst the affiliated agencies.\n\n### Instrument LID Prefix\nLID prefix for the Instrument lead agency. If there is not a clear lead agency, then this is determined via discussion amongst the affiliated agencies.\n\n************************************\n\n## Using GitHub Tools to Create and Update Products\n\nThis section provides a fair amount of detail and some recipes for creating and editing \ncontext product files that are destined to be incorporated into the official \nNASA-PDS/pds4-context-products repo. Because only EN has write access to the official \nrepo, a bit of extra procedure is required to submit your own edits and additions. \n\n- [Prerequisites](#prerequisites)\n- [The Overall Workflow](#the-overall-workflow)\n- [1. Raising an Issue](#1-raising-an-issue)\n- [2. Forking the NASA-PDS Repo](#2-forking-the-nasa-pds-repo)\n- [3. Creating a Branch](#3-creating-a-branch)\n- [4. Editing the Working Copy](#4-editing-the-working-copy)\n  - [Using the GitHub Text Editor](#using-the-github-text-editor)\n  - [Using the GitHub Desktop App](#using-the-github-desktop-app)\n  - [Using git CLI](#using-git-cli)\n- [5. Filing a Pull Request (PR)](#5-filing-a-pull-request-pr)\n- [EN Processing](#en-processing)\n- [Cleaning Up Your Repo](#cleaning-up-your-repo)\n\n### Prerequisites\n\nYou will need a GitHub account. Without an account you cannot raise issues in the NASA-PDS \nrepo. You will also need to create a personal working copy of the official repo in which to make\nand save your changes in your own account before submitting them to the NASA-PDS repo for \ninclusion.\n\nYou will be interacting with GitHub at some level. This can be through a web browser,\nthe git command line interface (\"git CLI\"), through the GitHub Desktop app, or through some \nother method you've already learned. Basic instructions for the three common options just \nmentioned are included below.\n\n### The Overall Workflow\n\nAs a reminder, here's the basic workflow:\n1. Raise an issue in the NASA-PDS repo if one does not already exist.\n2. Fork the NASA-PDS repo into your own GitHub account space to create a working copy.\n3. In your working copy of the repo, create a branch with a name that contains the issue \nnumber(s) of the related issue(s)\n4. Edit the branch of your working repo.\n5. When you're done, file a Pull Request in the [NASA-PDS4/pds4-context-products](https://github.com/NASA-PDS/pds4-context-products/pulls) repo to request that EN merge the branch from your working copy into the NASA-PDS repo.\n\nNow for the gory details...\n\n----\n### 1. Raising an Issue\n\nClick on the **Issues** tab in the upper left of the *NASA-PDS/pds4-context-products* repo \nhome page. Once on the **Issues** page, click the green **New Issue** button in the upper \nright.\n\nHere's a shortcut: [Raise a Context Product Issue](https://github.com/NASA-PDS/pds4-context-products/issues/new/choose)\n\nFollow the instructions given under [Raising Issues](#raising-issues), above, to complete \nthe process.\n\nOnce you've raised the issue, or if the issue already exists, click on the title of the issue \nin the **Issues** list to get to the page for that issue.\nIf you expect input from other collaborators, refer them to the comment stream on the page \nfor your issue. You can work the details here with any interested parties.\n\nWhen you're ready to start creating/editing context products, you will need to make your own \nworking copy of the repo.\n\n----\n### 2. Forking the NASA-PDS Repo\n\nIf you do not currently have a personal working copy of the *NASA-PDS/pds4-context-products* \nrepo, you will need to fork that repo.\nForking the repo makes an identical copy under your own GitHub account. \nFrom the **Code** page of the \n[NASA-PDS/pds4-context-products](https://github.com/NASA-PDS/pds4-context-products) repo, \nlook for the \"Fork\" button, located on the right \nabove the \"About\" side panel. Unless you know you want something different, the defaults will \nwork for the usual context product workflows.\n\nIf you *do* have an existing fork of the *NASA-PDS/pds4-context-products* in your GitHub\naccount, before starting new work you should click the \"Sync fork\" button (underneath the\ngreen \"\u003c\u003e Code\" button) to make sure your forked copy is up to date with the master.\n\n----\n### 3. Creating a Branch\n\nBack in your own account, in your working copy of *pds4-context-products*, create a new \nbranch with a name that \ncontains the number(s) of the issue(s) you're addressing and any additional notes you want \nto add. \n\nOn the **Code** page of your repo, there is a pull-down menu on the top left edge of \nthe file list window. It will probably say \"main\". Click on that to see the current list\nof branches. Typing a new branch name in the \"Find or create a branch...\" box and hitting\n*Return* will create a new branch with the entered name.\n\nSome example branch names:\n- issue_42\n- update_target_cg_issue67\n- issues34and36\n\n----\n### 4. Editing the Working Copy\n\nAt this point you are ready to start editing in your new branch. \nWhen it comes to making changes in your repo, there are several options. Any will work.\nThree of the most common options are described in detail below:\n1. In a browser, using the GitHub text editor\n2. On your local system, using the *GitHub Desktop* app\n3. On your local system, using *git CLI (Command Line Interface)*\n\n#### Using the GitHub Text Editor\n\nGo to the **Code** page for your working copy of *pds4-context-objects* and make sure you are \non the branch you created by checking the button on the left under the repo name. It should \n*not* say \"main\". If it does, pull down the menu and select the branch you created for this \nissue.\n\nOnce on the editing branch, in the folder list click on *data/pds4* and then *context-pds4*. \nThen navigate to the folder where you want to add or update a context object. Follow the \ninstructions in the [README for the repo](README.md) to either [add](README.md#to-create-a-new-context-product) or [update](README.md#to-update-an-existing-context-product) the product.\n\n- To create a new file, click the **Add File** menu in the upper right corner. \n- To edit an existing file, including one that has been renamed, \nfirst select the file to show the current contents, then click on the pencil \nicon in the upper right of the file display window to edit the file. \n- To rename a file, open \nit in the editor and edit the file name in the edit box above the content display. The edit \nbox is at the end of the file path.\n\nWhen you are done editing, click the green *Commit changes* button in the upper right, add an \nappropriate commit comment, make sure you're committing to the branch you created and not \n\"main\", and click the green *Commit changes* button at the bottom of the pop-up window to \nmake it all official.\n\n#### Using the GitHub Desktop App\n\nIn GitHub Desktop, start by cloning your working copy from GitHub to your local disk space:\n  - Open the *Current Repository* drop-down menu \n  - Open the *Add* drop-down menu\n  - Select \"Clone repository...\"\n  - Select the tab for your preferred method for cloning repos\n\nIf you don't have a \"preferred method for cloning\", try *URL*. In a browser, go to your \nworking copy of the *pds4-context-objects* repo in GitHub, \nopen the drop-down menu for the green \n**Code** button, select the \"Local\" tab and then \"HTTPS\". Click the copy icon to copy the \nrepo URL, which you can then paste into the URL box in GitHub Desktop. In Desktop, modify the \n\"Local \npath\" as desired and click the blue **Clone** button. If you already created the branch on \nGitHub, then make sure you select the option to download all branches (not just \"main\"). If \nyou didn't, you can create the branch locally once the repo is cloned, but you should then \npublish that branch back to your working repo on GitHub.\n\nSelect your cloned working repo (if you just cloned it, it should be set automatically); then \nselect your editing branch from the *Current Branch* drop-down menu. (Create a branch if none \nexists and publish it.)\n\nYou can now edit, add, and rename files using your usual local methods (editors, file \nexplorers, etc.). Git will track your changes. When  \nyou're done, commit the changes to your branch, and then push those changes to the \nsame branch in your working repo on GitHub.\n\n#### Using git CLI\n\nHere is a [Git CLI Cheat Sheet](https://education.github.com/git-cheat-sheet-education.pdf) \nif you need a quick reference. \nThe following assumes you have already performed initialization and credential setup for your \nlocal git instance. \n\nIn a browser, navigate to the **Code** page for your working *pds4-context-products* repo. \nOpen the drop-down menu on the green *\u003c\u003e Code* button, select the \"Local\" tab, and click the \ncopy icon to copy the URL of your working repo to your clipboard.  Important: you must select the SSH tab, as HTTPS will not work for upload.\n\nAt your local command line, start by moving to the directory where you want to create the \nlocal copy of your working *pds4-context-products* repo. Then do:\n```\ngit clone [pasted URL]\n``` \nThis will create a copy of the \"main\" branch of your repo. Move down one level to the \ndirectory just created (it will be called \"pds4-context-objects\" unless you specifically did\nsomething to rename it). \n\nIf you already created an editing branch on GitHub, switch to editing that branch by doing:\n```\ngit checkout [branchname]\n```\nIf you didn't, you can create one locally now and then switch to it:\n```\ngit branch [branchname]\ngit checkout [branchname]\n```\nNow you can edit files in the directory tree (you should only be working in \nthe ```data/pds4/context-pds4``` directories) and the changes will be logged to the new \nbranch. \n- To add a new file, navigate to the directory where the file resides and\ndo ```git add [newfilename]``` to stage the new file before committing your changes\nto the branch.\n- To rename a file, do ```git mv [oldfilename] [newfilename]```. \n- To edit an existing file, including one that has been renamed, use your favorite \ntext editor.\n\nWhen you're done editing and are ready to upload your changes to \nGitHub, first do ```git status```. This will list any discrepancies - like new files you forgot to \n```git add``` - that should be resolved before uploading changes to your working repo. When \nany problems have been resolved and you're ready to publish, \ndo ```git push``` to upload your changes to your editing branch in GitHub.\n\n----\n### 5. Filing a Pull Request (PR)\n\nOnce you've got your changes uploaded to, or otherwise incorporated into, your editing branch \nin your working repo, it's time to request that your proposed changes be merged into the \nofficial repo via a *pull request* (PR).\n\nTo do this, go to the \n[NASA-PDS4/pds4-context-products](https://github.com/NASA-PDS/pds4-context-products) repo, \nclick on the **Pull requests** tab in the upper left, and click on the green **New pull \nrequest** button. Or use this shortcut: \n[Create a PR on the Context Product Repo](https://github.com/NASA-PDS/pds4-context-products/compare).\n\nYou will probably see something very much like this:\n\n![Pull Request Display](images/PR-HowTo-1.png)\nThe grey bar provides two drop-down menu bottons. One of these is labeled \"base: main\". This \nis where we want our changes to end up - the main branch of the NASA-PDS repo. Next to this \nis an arrow that points to the left, indicating that changes will be pulled from the right to \nthe left. The other drop-down, on the right, is labeled \"compare: main\", and if you click on \nit you will only see other branches in the NASA-PDS repo. We don't want any of those.\n\nNow look *above* that grey bar, to the blue text under the **Compare changes** title that \nreads, \"compare across forks\". Click on that blue text and you should now see this:\n\n![Expanded PR Display](images/PR-HowTo-2.png)\nThere are now two drop-down buttons on each side of the arrow. On the **right** side of the \narrow, the fork you made of the NASA-PDS repo should be listed. Click on the drop-down and \nselect it. Once you have done that, you can now click on the last drop-down to select the \nbranch that contains the edits you made. \n\nIf you have recently pushed a commit to your own working branch and then create a PR in\nthe NASA-PDS repo, you may get a helpful screen like this one instead:\n\n![PR Display with fork commit referenced](images/PR-HowTo-3.png)\nThe yellow bar here is noting a recent commit to a document development branch, and provides the handy green \"Compare \u0026 pull request\" button. Clicking on this opens a new\npull request with the appropriate branches all set, and a form to be filled out. Follow\nthe instructions to provide the appropriate title and text.\n\nTo reference the issue(s) you're addressing, start with the '#' character, and you should get a list of open issues to select from. For example:\n\n![PR Showing issue selection list](images/PR-ShowIssueList.png)\nIf you've validated your context product(s), you can indicate that under \"Test Data\nand/or Report\".\n\nWhen you've completed the form, click the green \"Create pull request\" button on the lower\nright.\n\n## EN Processing\n\nEN personnel will be notified of the pull request. They will review it and you may be \ncontacted if they have questions or if there is some conflict with existing products or \nrequirements. EN will also merge the request when the review is complete.\n\n## Cleaning Up Your Repo\n\nYou should get an email notification from GitHub when your PR is merged into the NASA-PDS4 \nrepo. At that point, if you are not planning to contribute any more modifications, you \ncan delete your copy of the repo. To do this, go to the **Settings** tab of your repo and\nscroll down to the bottom section entitled \"Danger Zone\". At the end of the list of \ndangerous actions\nis a button labeled \"Delete this repository\". If you really want to delete it, this is the\nbutton to click.\n\nIf you think you will be working in this repo again, then *after your PR is merged*, \nyou should click on \nthe \"Sync fork\" button to add any changes made to the *NASA-PDS/pds4-context-products*\nmaster (including the changes from your PR) into the main branch of your local copy. \nYou can then delete the branch you no longer need by clicking \non the \"Branches\" tab\n(next to the \"main\" drop-down menu on the upper left). This will display tables listing\nthe existing branches. Click the trash can icon on the right of a branch row to delete\nthe branch. \n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnasa-pds%2Fpds4-context-products","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnasa-pds%2Fpds4-context-products","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnasa-pds%2Fpds4-context-products/lists"}