search

techservicesillinois / secdev-robot

Examples in RobotFramework for automated testing of mobile applications
Other
1 stars 0 forks source link

Remaining Prep to Open Source #20

Closed edthedev closed 3 years ago

edthedev commented 3 years ago
mpitcel commented 3 years ago

FYI, this repository has the License file ( https://github.com/techservicesillinois/secdev-robot/blob/master/LICENSE ), and has EOL details ( https://github.com/techservicesillinois/secdev-robot/blob/master/README.md )

mpitcel commented 3 years ago
  • ensure main branch is named 'main'.
  • go through the 'community' steps in GitHub Settings.
  • ensure end of life and open source license are applied.

Clarification questions:

edthedev commented 3 years ago

What is the proper way to create a 'main' instead of a 'master' branch? Should it just be renamed?

Yep. There's a 'rename' button in the GitHub interface. After renaming, each person who has a version checked out will need to git checkout the new main branch.

edthedev commented 3 years ago

What are the 'community' steps? I did not see them in the 'Settings' tab.

It's normally under Insights in the menu at the top. But it looks like it doesn't appear until after the repository has been open-sourced. - I get a 404 when I try to directly visit https://github.com/techservicesillinois/secdev-robot/community

mpitcel commented 3 years ago

What is the proper way to create a 'main' instead of a 'master' branch? Should it just be renamed?

Yep. There's a 'rename' button in the GitHub interface. After renaming, each person who has a version checked out will need to git checkout the new main branch.

Thanks for the information - I just wanted to be sure there was not a protocol I missed.

I will go ahead and make this change today.

UPDATE: Change made. Users with old 'master' checked out will need to do the following on their local machine:

git branch -m master main

git fetch origin

git branch -u origin/main main

git remote set-head origin -a
edthedev commented 3 years ago

I've created #21 to track the community work, which must be done after making the repository public.

🎉🎉 Looks like we're ready! 🎂🎉🎉

Please go ahead and make the repository public.

edthedev commented 3 years ago

We're going to do static secret check scan #22 and then publish.