🚀 [QA] Update release environment #549
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Use locally saved data to get most of the informations about XP
The current tracking is just that the user hit the page. It's double- tracking on dev, need to check that this doesn't happen in prod.
It feels a little wobbly here, but assuming it works, it should give us a way to see if people start staking and fail to complete, or same with unstaking, in case there are wallet issues or similar.
The `github.head_ref` variable does not include the `ref/heads/` part.
The `github.head_ref` variable does not include the `ref/heads/` part.
Ref #503 Adjusting xp allocations since the start date do not match with contracts
Ref #503 What has been done: - Correct start date was hard-coded - Calculation of the current season week was adjusted depending on if the season has already started
Resolves #509 Adding extra check to not render the "first visit to realm" assistant pop-up if user is already staked
Resolves #531 Change favicon to Subscape
Resolves: #529 <img width="1726" alt="Screenshot 2023-10-26 at 10 09 10" src="https://github.com/tahowallet/dapp/assets/28560653/0c4f9f3b-7394-4a84-8c58-ef88582daf5d">
Resolves: #527 <img width="700" alt="Screenshot 2023-10-26 at 10 14 19" src="https://github.com/tahowallet/dapp/assets/28560653/8b7406c6-6647-46a2-8d20-da2859d9a90f">
Resolves: #525
Resolves: #524
Resolves: #530 <img width="389" alt="asistant_welcome" src="https://github.com/tahowallet/dapp/assets/28560653/cece0e70-b1d2-458d-ad69-ba1bd71014b7"> <img width="395" alt="assistant_first_realm" src="https://github.com/tahowallet/dapp/assets/28560653/4d1e3131-5872-4876-a8d2-64904754d75f"> <img width="402" alt="assistant_join" src="https://github.com/tahowallet/dapp/assets/28560653/90fb7d6a-872a-426f-9036-cc5450958ead"> <img width="395" alt="assistant_quests" src="https://github.com/tahowallet/dapp/assets/28560653/9170c7c2-25ee-4fbb-aff7-47fae06e9119">
Resolves #521 What has bee done: - Changed the entering animation of realm modal
Closes #503 For now let's just hardcode the weekly reward.
We never put this explicitly on the roadmap, but it would be good to get a little better feel for how people are using the dApp, and be able to compare against the wallet info. A few notes: - I haven't been able to test extensively, and in particular am not fully convinced of the approach for staking/unstaking. It's built to track the beginning and end of that process, so we can see if people are starting to stake/unstake and then not making it through to transaction completion. - Priority-wise, I'd like to have pageviews (the first commit) at launch, then if possible realm opens, and then if we're feeling good about it the staking/unstaking stuff. To some extent we can do staking/unstaking on-chain, so it's not quite as critical. - We'll want to set up the ANALYTICS_ENV and POSTHOG_API_KEY variables appropriately. Right now I'm just using the API key from taho.xyz. The default analytics env is DEV, we'll want PROD for the released dApp. Torch-passing here, let's consider pageview + realm opens as second priority to any blockers, but higher priority than any nice-to-haves for launch. Leaving this in draft as I realize we may need to cherry-pick partial commits and such to get the outcome we're most comfortable with.
This is a pull request that upon merging will update stage environments with recent `main` changes. The environments that will be updated: * Stage live: https://stage-live--taho-development.netlify.app/ * Stage fork: https://stage-fork--taho-development.netlify.app/ Read more: [Deployment to Production Flow](https://github.com/tahowallet/dapp/blob/main/docs/testing-env.md)
✅ Deploy Preview for taho-development ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Release checklistThis release checklist should be performed before release is published.
Approve the PR when the checklist is finished ✅ Merge the PR when it is approved and we want to update the production Manual tests
|
michalinacienciala
approved these changes
Oct 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a pull request that upon merging will update production environment with recent
stage-livechanges.The environment that will be updated:
Read more: Deployment to Production Flow