Skip to content

Conversation

@pbrisbin
Copy link
Member

  1. Flip rule about .sh to align with current convention
  2. Fix invalid markdown links
  3. Update CI recommendation
  4. Remove reference to FRTool

1. Flip rule about `.sh` to align with current convention
2. Fix invalid markdown links
3. Update CI recommendation
4. Remove reference to FRTool
@pbrisbin pbrisbin requested a review from a team as a code owner June 25, 2025 16:56
@pbrisbin pbrisbin requested review from derelbenkoenig and jason-lieb and removed request for a team June 25, 2025 16:56
@pbrisbin pbrisbin enabled auto-merge (rebase) June 25, 2025 17:03
@pbrisbin pbrisbin merged commit 5470173 into main Jun 25, 2025
1 check passed
@pbrisbin pbrisbin deleted the pb/shell branch June 25, 2025 17:03
Comment on lines +14 to +19
An executable shoudl be opaque and not leak its implementation language. If a
script is meant to be used as libaray (e.g. with `source`), then it can end in
a `.sh` extension but should not be marked exsecutable.

We use to require a `.sh` extension so CI could locate files for linting, but
that is no longer how that works.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Holy cow there are some typos here. That's what I get for editing in the GitHub UI I guess :/

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.

3 participants