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.

Sign up for GitHub

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

Jump to bottom

Doing everything correctly but getting a cross while deploying to Azure #89

Closed
protonerdy opened this issue Jan 13, 2024 · 15 comments
Closed

Doing everything correctly but getting a cross while deploying to Azure #89

protonerdy opened this issue Jan 13, 2024 · 15 comments

Comments

@protonerdy
Copy link

image
When I click on create a static page, after filling all the details, I'm getting this cross which makes my webpage come to default with "Alexandrie Grenier" instead of my name. Please help! I've tried 4-6 times now and I'm getting the same error.
@AnthonyByansi
Copy link
Contributor

Hi @protonerdy had you looked at Step 3 precisely?
These are the details you need to to change
image

@protonerdy
Copy link
Author

image
Yes @AnthonyByansi I have used my own details.

@theyashsisodiya
Copy link

It is yellow mean it's mean the code is modified save the change or commit the change in your repo.

@protonerdy
Copy link
Author

image
@theyashsisodiya
Getting this error, and here are the logs:

2024-01-23 13:52:16.761 [info] Validating found git in: "git"
2024-01-23 13:52:16.761 [info] Using git "2.43.0" from "git"
2024-01-23 13:52:16.761 [info] > git rev-parse --show-toplevel [6ms]
2024-01-23 13:52:16.761 [info] > git rev-parse --git-dir --git-common-dir [2ms]
2024-01-23 13:52:16.761 [info] Open repository: /workspaces/MLSA-Portfolio
2024-01-23 13:52:16.761 [info] > git config --get commit.template [37ms]
2024-01-23 13:52:16.761 [info] > git rev-parse --show-toplevel [24ms]
2024-01-23 13:52:16.761 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [18ms]
2024-01-23 13:52:16.761 [info] > git rev-parse --show-toplevel [9ms]
2024-01-23 13:52:16.761 [info] > git rev-parse --show-toplevel [42ms]
2024-01-23 13:52:16.774 [info] > git status -z -uall [16ms]
2024-01-23 13:52:16.809 [info] > git rev-parse --show-toplevel [36ms]
2024-01-23 13:52:16.811 [info] > git config --get commit.template [1ms]
2024-01-23 13:52:16.852 [info] > git rev-parse --show-toplevel [20ms]
2024-01-23 13:52:16.865 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [15ms]
2024-01-23 13:52:16.879 [info] > git rev-parse --show-toplevel [14ms]
2024-01-23 13:52:16.893 [info] > git status -z -uall [15ms]
2024-01-23 13:52:16.897 [info] > git rev-parse --show-toplevel [5ms]
2024-01-23 13:52:16.912 [info] > git rev-parse --show-toplevel [2ms]
2024-01-23 13:52:17.222 [info] > git check-ignore -v -z --stdin [2ms]
2024-01-23 13:52:19.914 [info] > git check-ignore -v -z --stdin [805ms]
2024-01-23 13:52:20.351 [info] > git show --textconv :src/App.jsx [269ms]
2024-01-23 13:52:20.351 [info] > git ls-files --stage -- /workspaces/MLSA-Portfolio/src/App.jsx [244ms]
2024-01-23 13:52:21.357 [info] > git cat-file -s 13265c2108efe8e7c65edbf38a92ac058769af68 [984ms]
2024-01-23 13:52:25.161 [info] > git config --local branch.main.github-pr-owner-number [110ms]
2024-01-23 13:57:24.348 [info] > git config --local branch.main.github-pr-owner-number [1ms]
2024-01-23 14:01:10.593 [info] > git show --textconv :src/Components/Home.jsx [31ms]
2024-01-23 14:01:10.594 [info] > git ls-files --stage -- /workspaces/MLSA-Portfolio/src/Components/Home.jsx [2ms]
2024-01-23 14:01:10.634 [info] > git cat-file -s 30b53a54027fabfab1b88bafe490b50972fe1aa6 [3ms]
2024-01-23 14:01:17.413 [info] > git config --get commit.template [37ms]
2024-01-23 14:01:17.414 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [2ms]
2024-01-23 14:01:17.451 [info] > git status -z -uall [3ms]
2024-01-23 14:01:22.418 [info] > git check-ignore -v -z --stdin [2ms]
2024-01-23 14:01:22.513 [info] > git config --get commit.template [30ms]
2024-01-23 14:01:22.514 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [2ms]
2024-01-23 14:01:22.543 [info] > git status -z -uall [2ms]
2024-01-23 14:01:23.803 [info] > git merge-base refs/heads/main refs/remotes/origin/main [2ms]
2024-01-23 14:01:23.833 [info] > git rev-list --count --left-right refs/heads/main...refs/remotes/origin/main [2ms]
2024-01-23 14:01:26.573 [info] > git log --oneline --cherry main...main@{upstream} -- [73ms]
2024-01-23 14:01:27.119 [info] > git pull --tags origin main [516ms]
2024-01-23 14:01:27.119 [info] From https://github.com/protonerdy/MLSA-Portfolio
 * branch            main       -> FETCH_HEAD
hint: You have divergent branches and need to specify how to reconcile them.
hint: You can do so by running one of the following commands sometime before
hint: your next pull:
hint: 
hint:   git config pull.rebase false  # merge
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: 
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
fatal: Need to specify how to reconcile divergent branches.
2024-01-23 14:01:27.178 [info] > git config --get commit.template [28ms]
2024-01-23 14:01:27.180 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [1ms]
2024-01-23 14:01:27.210 [info] > git status -z -uall [3ms]
2024-01-23 14:01:28.392 [info] > git config --get commit.template [28ms]
2024-01-23 14:01:28.393 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [2ms]
2024-01-23 14:01:28.424 [info] > git status -z -uall [3ms]
2024-01-23 14:01:28.600 [info] > git ls-files --stage -- /workspaces/MLSA-Portfolio/src/Components/Home.jsx [1ms]
2024-01-23 14:01:28.629 [info] > git cat-file -s 30b53a54027fabfab1b88bafe490b50972fe1aa6 [1ms]
2024-01-23 14:01:28.806 [info] > git show --textconv :src/Components/Home.jsx [3ms]
2024-01-23 14:01:40.050 [info] > git log --oneline --cherry main...main@{upstream} -- [4ms]
2024-01-23 14:01:40.568 [info] > git pull --tags origin main [488ms]
2024-01-23 14:01:40.568 [info] From https://github.com/protonerdy/MLSA-Portfolio
 * branch            main       -> FETCH_HEAD
hint: You have divergent branches and need to specify how to reconcile them.
hint: You can do so by running one of the following commands sometime before
hint: your next pull:
hint: 
hint:   git config pull.rebase false  # merge
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: 
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
fatal: Need to specify how to reconcile divergent branches.
2024-01-23 14:01:40.629 [info] > git config --get commit.template [31ms]
2024-01-23 14:01:40.629 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [2ms]
2024-01-23 14:01:40.662 [info] > git status -z -uall [3ms]
2024-01-23 14:01:41.939 [info] > git config --get commit.template [30ms]
2024-01-23 14:01:41.939 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/main refs/remotes/main [3ms]
2024-01-23 14:01:41.970 [info] > git status -z -uall [2ms]
2024-01-23 14:01:42.144 [info] > git ls-files --stage -- /workspaces/MLSA-Portfolio/src/Components/Home.jsx [2ms]
2024-01-23 14:01:42.173 [info] > git cat-file -s 30b53a54027fabfab1b88bafe490b50972fe1aa6 [2ms]
2024-01-23 14:01:42.352 [info] > git show --textconv :src/Components/Home.jsx [2ms]```

@theyashsisodiya
Copy link

Watch this video do the same process as shown in this video : https://youtu.be/ywnEk471oKs?si=kbUH8Qdb_LXsN_dK

@protonerdy
Copy link
Author

@theyashsisodiya that video aims to create the Cloud Skill Challenge, there's no information about the Technical Onboarding.

@theyashsisodiya
Copy link

@theyashsisodiya that video aims to create the Cloud Skill Challenge, there's no information about the Technical Onboarding.

Sorry for that mistake check out this video : https://youtu.be/tl4vk64enKA?si=RwSYySd10InlqRYr

@KarlaaLinares
Copy link

Hola. tuviste solucion?
es que tambien tengo el mismo problema que tu

@theyashsisodiya
Copy link

theyashsisodiya commented Feb 8, 2024 via email

@AnthonyByansi
Copy link
Contributor

hi @theyashsisodiya please note that for Alpha advancement, you need to at least complete any of the following Learn paths. If you happen to have finished any of those, note that Alpha milestone advancement is automated and can take 2-3 weeks from the time you completed the learning,

In the meantime, you can check for your Certificate from the MVP website at the downloads section
image

@theyashsisodiya
Copy link

theyashsisodiya commented Feb 9, 2024 via email

@AnthonyByansi
Copy link
Contributor

Hi @theyashsisodiya you were meant to download your Alpha Certificate early on. I'm not quite sure whether that could be reversed. Please reach out to the SA-coordinator on teams to have you assited

@theyashsisodiya
Copy link

@AnthonyByansi I have tried and told them about my concern but they didn't understand and at the end they sent a mail that the ticket is resolved!!

@SalemTracey
Copy link
Collaborator

@theyashsisodiya - it is possible for us to retrigger the Alpha certificate. i'll send a chat to you via Teams.

cc @AnthonyByansi

@theyashsisodiya
Copy link

Sure! @SalemTracey , your help would be greatly appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@protonerdy @theyashsisodiya @AnthonyByansi @SalemTracey @KarlaaLinares