zopencommunity / zopencommunity/bashport
Introduce _ENCODE_FILE_EXISTING env variable
Open
- Dominant language
- Groovy
- Stars
- 12
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Use the z/OS UNIX environmental variables, _ENCODE_FILE_NEW and _ENCODE_FILE_EXISTINGto control bash processing and tagging of new files and existing untagged files.
Issue Originated from - https://ibm-systems-z.slack.com/archives/C039TNSH9J5/p1772211070607389
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the issue description and linked pull request #105 first, then locate the bash processing and file-tagging entry points involved in _ENCODE_FILE_NEW. Extend the same behavior to _ENCODE_FILE_EXISTING for existing untagged files, and verify that both environment variables control their respective cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100