-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a new Code of Conduct Page #4249
Comments
@ExperimentsInHonesty - I am testing out ways to do this. I looked at your Diff analysis and I was confused. Do you want the CODEOFCONDUCT.md file that currently exists in the website repo to just be a hard copy of the CODEOFCONDUCT.md in hackforla/codeofconduct? Or do you want the page to dynamically render from hackforla/codeofconduct without holding a hard copy inside the repo? I was also not sure what the Feature label should be. |
@jdingeman Use the same feature labels as the ones I put on this issue Yes, I want to dynamically render from hackforla/codeofconduct without holding a hard copy inside the repo if possible. That way we are always only updating it in one place and that place is appropriate for all teams to link to. |
@ExperimentsInHonesty - I think it's possible using the GitHub API, but I think this will be considered a large issue. Please see DRAFT NOTES for potential roadblocks/questions. |
@jdingeman I think that if we do this
Then it's going to look weird because there is no header image and text. For now, let's just have it be |
Hi @bootcamp-brian, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
Availability for this week: Weekdays before 5pm |
Provide Update
|
@ExperimentsInHonesty - From my research into this issue, using the GitHub REST API to get the info from the README.md file in the hackforla/codeofconduct repo doesn't seem like a great solution because it would require a lot more work in terms of parsing the data and doing a lot of DOM manipulation. I think I've come up with a good alternative, though. If we use a GitHub action created in the hackforla/codeofconduct repo that triggers whenever the README.md file gets updated and uses GitHub REST API to copy that file's contents and create or update a corresponding .md file in the _includes directory of the website repo, we can then easily include that file on the code of conduct page while maintaining the markdown formatting from the original file. This would technically have a hard copy in the website repo, but its maintenance would be automated. I believe I've worked out the code to do this for the most part, but only someone who has write access to the hackforla/codeofconduct repo would be able to implement it. Does this suggestion accomplish what you wanted and sound like a good option to you, Bonnie? Let me know how you want me to move forward with this issue. |
Provide Update
|
Provide Update
|
Overview
Since HfLA is no longer bound by Code for America's Code of Conduct, we need to update HfLA's Code of Conduct. For this issue, you will need to create a new Code of Conduct page so that developers will read the Code that pertains to HfLA specifically.
Action Items
layout: default
permalink: code-of-conduct
so Jekyll can build the pageInclude the file in index.htmlFor PM/Tech Lead/Merge Team
Resources/Instructions
The text was updated successfully, but these errors were encountered: