Skip to content

Commit

Permalink
Add recommendation on upstream remote
Browse files Browse the repository at this point in the history
  • Loading branch information
mdpiper committed Aug 9, 2024
1 parent b611e67 commit b9b941f
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions lessons/best-practices/collaboration-etiquette.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,8 @@ for working on a collaborative project.

1. Don't hardcode model configuration values; use a configuration file in a plain text format like cfg, yaml, or toml, and read in the values.

1. You don't need an upstream remote when you own a repository. If your team or organization owns a repository, an upstream remote may not be necessary (depending on org rules or practices), but it may still be a good idea.

1. Avoid including data (input or output) in a source code repository. There's some gray area for data
used in an example, but the data should be small.

Expand Down

0 comments on commit b9b941f

Please sign in to comment.