|
| |||||||||
|
| |||||||||
|
Your hackathon environment closes on [closure date]. Export anything you want to keep. | |||||||||
Thank you — [number] teams, [number] published applications, one day. Everything you built lives in the temporary GitHub organisation we created for the workshop. On [closure date] that organisation, every repository inside it and every published address from the day will be permanently deleted. There is no backup and nothing can be recovered afterwards. Please take five minutes now to save your work. | |||||||||
|
| |||||||||
|
THREE WAYS TO KEEP YOUR WORK | |||||||||
|
|
| ||||||||
|
Transfer it to your own organisation |
Download a copy | ||||||||
The best option. An owner of your company's GitHub organisation can accept a transfer: open your repository, then Settings, General, Danger Zone, Transfer ownership. Everything moves with it, including the workflow that publishes the site. Agree it with your IT contact first. Ask your IT contact first | The quickest option, and it works for everyone. On the repository page choose Code, then Download ZIP. You get every file, though not the history. Save it somewhere your team will still be able to find it in six months. Code → Download ZIP | ||||||||
|
Keep a record of the live site | |||||||||
The published address stops resolving on [closure date]. The site itself is rebuilt from the files in your repository, so a transfer or a ZIP already contains everything needed to publish it again — there is no separate download for the website. For your write-up, take a few screenshots and a short screen recording while the address is still live. A thirty-second clip of the thing working is worth more in a steering meeting than any slide about it. | |||||||||
|
WHAT HAPPENS ON [CLOSURE DATE] | |||||||||
| |||||||||
| |||||||||
|
WHAT HAPPENS NEXT | |||||||||
|
Your idea already has an owner and a decision | |||||||||
At the end of the day your sponsor triaged every idea in the room: keep and grow, park with a reason, or hand to IT. That list went to your sponsor and your IT contact, together with the guardrail set and the best-practice playbook from the day. If your idea was picked up, someone will be in touch about the route to production. If it was parked, the reason is written down and it keeps its place in the list rather than disappearing. | |||||||||
|
| |||||||||
Questions? Reply to this email and we will come back to you. Privacy Statement | Unsubscribe Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 USA | |||||||||
|
| |||||||||
