it depends on a rank/role
in most of cases:
you get available list of tasks to perform (there would be prioritization highly likely what to do first)
you do some task, research how to have it done
creating git branch
write your code that explores solution / refactoring / writing tests
pushes your solution to remote git
when you open merge/pull request into master branch, it triggers for sure CI pipeline that runs unit and linting tests at least, if it is green, a person is invited for code review
your code is reviewed, you fix little things
it is eventually merged into master
then eventually master branch runs CI pipeline with unit and linting tests again, and also deploys current version of application into staging infrastructure enviroment where it gets tested with automated tests or with manual QA
if it goes well, tasks is marked as completely done, otherwise additional fixes are requested, in some cases your merged solution is reverted until fixed one is gained
additionally to this workflow if they are from US/EU, they can be following SCRUM stuff
if you are senior role and even having leader level positions in a project:
you can be also planning the project / its direction of development
and distributing tasks to complete between other developers and you included xD