Add new_projects.md #14

todtb · 2023-08-08T01:12:11Z

todtb commented

2023-08-08 01:12:11 +00:00

No description provided.

todtb added 1 commit 2023-08-08 01:12:11 +00:00

Add new_projects.md b575258352

scott requested changes 2023-08-08 13:59:52 +00:00

new_projects.md Outdated

					
				@ -0,0 +1,6 @@

				# New projects

				## Initializing the repo

				1) Create the repo first

scott commented

2023-08-08 13:58:26 +00:00

"and clone it"

new_projects.md Outdated

					
				@ -0,0 +2,4 @@

				## Initializing the repo

				1) Create the repo first

				2) Push an empty commit to the `main` branch with the message `init`

scott commented

2023-08-08 13:18:05 +00:00

I don't think you can create an "empty commit". Perhaps one should do this?

touch .gitignore
git add .gitignore
git commit -m init
git push -u upstream main

I don't think you can create an "empty commit". Perhaps one should do this? ```console touch .gitignore git add .gitignore git commit -m init git push -u upstream main ```

new_projects.md Outdated

					
				@ -0,0 +3,4 @@

				## Initializing the repo

				1) Create the repo first

				2) Push an empty commit to the `main` branch with the message `init`

				3) All further work to be merged from a branch on a fork

scott commented

2023-08-08 13:59:34 +00:00

I think more specific instructions are due here. Specifically, the process of changing a remote from origin to upstream after cloning it, adding your fork as a clone, checking out a branch named "prototype" and creating a PR for that.

evanb commented

2023-08-09 17:25:54 +00:00

So I just took some time and wrote up a step by step guide on how to create a new project based on this outline. I was wondering where the best place is to post it?

Should I fork and submit a PR from todtb-patch-1?
Create my own fork and PR into main?
Should we utilize the WIKI for documentation?

So I just took some time and wrote up a step by step guide on how to create a new project based on this outline. I was wondering where the best place is to post it? Should I fork and submit a PR from `todtb-patch-1`? Create my own fork and PR into `main`? Should we utilize the WIKI for documentation?

todtb commented

2023-08-10 01:47:30 +00:00

Create my own fork and PR into main?

Yeah, I guess it can't hurt to follow that practice even on the meta repo

Should we utilize the WIKI for documentation?

I like that idea! I think there's still value in the meta repo for documentation that doesn't apply strictly to a codebase, but I'm open to trying it out. I guess it could be the wiki on this repo too.

> Create my own fork and PR into main? Yeah, I guess it can't hurt to follow that practice even on the `meta` repo > Should we utilize the WIKI for documentation? I like that idea! I think there's still value in the `meta` repo for documentation that doesn't apply strictly to a codebase, but I'm open to trying it out. I guess it could be the wiki on this repo too.

evanb commented

2023-08-10 16:38:13 +00:00

I will PR for now but I too think there should be a place for random documentation. Something everyone can reference when they get started. Ill open an issue for discussion.