-
Notifications
You must be signed in to change notification settings - Fork 31
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
Redirect Principles.green to new Training website #109
Comments
@zanete hi. this one is not linked to any sprint yet. can you help schedule this in depending on Osama's availability? |
@holanita will meet with him today to discuss! :) |
this kind of stuff can only be done by @jawache |
@zanete ok noted. did you guys define an ETA for this? should I follow up with Asim? |
@holanita let's pause on this one till after we've also moved to greensoftware.org, otherwise there are too many changes in one go and it makes it harder to ensure things are working |
OK, I've updated the statuses accordingly. |
@jawache it's been a week now, do you think it's now a better time to implement? |
As discussed in today's team call, @jawache will do this today / tomorrow. |
Capturing the status during the weekly call:
|
Capturing the status during the weekly call:
|
I took a look and really am not sure what this is, it's just a GitHub site right @osamajandali? What key could this be? Do I need to give you some level of permissions? |
@jawache Could you try manual deploy from your end? just to see if this is the problem or not. And if there is more level of permission I can take please give it to me. |
Ahh ok, Ill try it on my old laptop |
Capturing the status during the weekly call:
|
Tried in several places, old laptop is fine. I can see it was erroring out on github pages with some strange error with deploy. The github actions config was using the v2 of something, the latest is v3 thought it might be that - rebuilding. jawache/principles-green@fe33b2a |
@osamajandali @jawache does this mean this is now a closed issue and all is working as expected? |
@osamajandali and @zanete can you take a look again, I think the error was in the versions of the actions. I've updated the config to use v3 but I think the rest of the config needs to change as between v2 and v3 the format of the file is diff. E.g. currently we use "env" but in the new v3 docs it seems to use "with" https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-set-ssh-private-key-deploy_key |
Capturing status in weekly call:
|
Capturing status in weekly call:
|
Capturing status in weekly call:
|
@osamajandali given that this is going to be a complete one-off last-ever change to this repo, can we just edit the gh-pages branch and push the changes manually to there? https://github.com/jawache/principles-green/tree/gh-pages |
@osamajandali given what Asim says above, have unblocked and put back in progress. |
Finally ! |
Why: the principles.green site still gets a decent amount of traffic, but the content is outdated
What: we should redirect traffic to the new page
Redirect from: https://principles.green/
Redirect to: https://learn.greensoftware.foundation/practitioner/introduction
To be discussed/confirmed if we should redirect pages one by one or you'll just redirect everyone to the main page regardless of which old principles.green subpage they land on?
@osamajandali can you get started on this one or do you need further info?
The text was updated successfully, but these errors were encountered: