Skip to content
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

Requesting a new PyLadies Chapter website: PyLadies Dublin #11

Closed
9 of 14 tasks
whykay opened this issue Jul 5, 2020 · 6 comments
Closed
9 of 14 tasks

Requesting a new PyLadies Chapter website: PyLadies Dublin #11

whykay opened this issue Jul 5, 2020 · 6 comments

Comments

@whykay
Copy link

whykay commented Jul 5, 2020

This template should be used for those requiring a new PyLadies website.

What is the name of the PyLadies chapter requesting the website?

PyLadies Dublin

What is the custom domain desired for the PyLadies chapter website?

Already have one: dublin.pyladies.com

What are the GitHub handles of the PyLadies chapter organizers?

Name GitHub Handle Slack Handle Team Role
Vicky Twomey-Lee @whykay @whykay - PyLadies Dublin Organiser

Do you want your website to use one of the following templates or do you prefer it to be blank?

Where will you host the website?

  • GitHub Pages
  • Heroku
  • Netlify
  • Other: [Please specify as this is needed for @pyladies/tech-and-infra-admins to setup the DNS record accordingly]

Issue checklist

For the author to complete:

For the @pyladies/tech-and-infra-admins to complete:

  • Insert link to repo:https://github.com/pyladies/pyladies-dublin-website
  • Is the custom domain created?
  • Are the organizers added to a PyLadies team with proper permissions for the repo? Insert name of the team: @pyladies/dublin
  • Is the GitHub team added to the repo with maintain permissions?

image

/cc @pyladies/tech-and-infra-admins

@whykay whykay changed the title Requesting a new PyLadies Chapter website: <Enter your PyLadies Chapter name> Requesting a new PyLadies Chapter website: PyLadies Dublin Jul 5, 2020
@lorenanicole
Copy link
Contributor

@whykay hi hi hi! OK so the intent here is for PyLadies to start streamlining our repos, moving the PyLadies chapter websites into our pyladies GitHub organization. That's why I made a for of your existing repo and made: https://github.com/pyladies/pyladies-dublin-website. I'll add this submodule and point the sub domain to this repo. You've been given all the powers for maintaining.

@lorenanicole
Copy link
Contributor

Question: Did you want the netlify preview setup on the https://github.com/pyladies/pyladies-dublin-website repo? If so, you'll need to add the netlify badge to your page e.g. like Chicago below.
image

@lorenanicole
Copy link
Contributor

@whykay can you follow up on the above? Or else we'll be moving to close this. Also are there any other coorganizers we should be inviting ?

@whykay
Copy link
Author

whykay commented Jul 28, 2020

Sorry, didn't get a chance to answer. Can you explain what you mean by "Did you want the netlify preview setup on the https://github.com/pyladies/pyladies-dublin-website repo?" - I don't know what I should be doing from my end as it's only on gitpages at the moment/

Thanks.

@lorenanicole
Copy link
Contributor

lorenanicole commented Jul 29, 2020

All I need to know @whykay is if you'd like to use Netlify to build previews for each PR that is opened against your gh-pages branch! Here's an example of how that works in the PyLadies Chicago website repo: pyladies/pyladies-chicago-website#1. Each time a PR is opened against your default branch (e.g. gh-pages if you host your website on GitHub pages) a preview is built to confirm the build looks as your expect. You can see if in the 'checks' that run via the deploy-preview check:

image

That gives you a deploy url like https://deploy-preview-2--thirsty-liskov-172d04.netlify.app/. We also use it on github.com/pyladies/pyladies. Example of a deploy preview from a recent PyLadies PR closed and merged: https://deploy-preview-531--pyladies.netlify.app/.

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants