How do I orchestrate my [transform].sql
in DAP⇨flow's dap-airflow
repository?
🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧
⚠️AWAITING COMPLETION⚠️
🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧
"We ♡ your feedback!"
👉 Please use this link ► DAP⇨flow UX
Feedback / github-orchestrate-transform
-
Your feedback enables us to improve DAP⇨flow and our Data Analytics Platform service.
-
We encourage all our users to be generous with their time, in giving us their recollections and honest opinions about our service.
-
We especially encourage our new users to give feedback at the end of every DAP⇨flow📚Migration onboarding task because the quality of the onboarding experience really matters.
☝ Please use this link to help us understand your user experience!
📚UX
Criteria
- Hackney Google Workspace user
- Hackney
[service]
Data Analyst - GitHub user
How do I orchestrate my [transform].sql
in DAP⇨flow's dap-airflow
repository?
Measures the GitHub and dap-airflow
repository behavior.
Given in my web browser, I am logged on to my GitHub account using my Hackney email address with two-factor authentication
~and I am granted membership of London Borough of Hackney organization on GitHub incorporating the dap-airflow
private repository
~and I previously committed my [transform].sql
directly to my [transform branch]
~and I have [transform].sql
open on another screen or separate browser tab where i can refer to it and copy any part of it into my computer's clipboard
When I select my [transform branch]
as my working branch
~and I navigate to my dap-airflow/airflow/dags/
[service folder]/[orchestration folder]
service subfolder
🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧
⚠️AWAITING COMPLETION⚠️
🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧
~and I click the "Commit changes" button to open up a dialogue box
~and I enter a short commit message, Eg. Add ... [transform].sql
~and I enter a longer description if I want to
~and I select the option “Commit directly to my [transform branch]
~and I click the "Commit changes" button
Then I should see a message telling me, my ...
was successfully committed directly to my [transform branch]
~and I will be permitted to make further edits to my [transform].sql
followed by commits to my to my [transform branch]
, as often as I need to, until I raise a pull request for my [transform branch]
.
Scale of ... to ... ~and flow features.