git help status


git status | more
On branch qa
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   package-lock.json
        modified:   package.json
        modified:   src/services/index.js
        modified:   yarn.lock

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        src/models/orders.model.js
        src/models/products.model.js
        src/services/orders/
        src/services/products/
        test/services/orders.test.js
        test/services/products.test.js

no changes added to commit (use "git add" and/or "git commit -a")


git add -a --dry-run

git add -A --dry-run
add 'src/services/offers/offers.hooks.js'
add 'src/services/trades/trades.hooks.js'

git add -A




git commit --dry-run

git commit --dry-run
On branch dev
Your branch is up to date with 'origin/dev'.

Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: src/services/offers/offers.hooks.js
modified: src/services/trades/trades.hooks.js


git commit -m 'my message - author'

git commit -m 'fixed trade accounting, offer status - jim'
On branch dev
Your branch is ahead of 'origin/dev' by 1 commit.
(use "git push" to publish your local commits)

nothing to commit, working tree clean




git push --atomic --dry-run

git push --atomic --dry-run
To github.com:Paramount-Software-Solutions/ebc-api.git
a5d33e6..d151083 dev -> dev


git push --atomic

Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 8 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 1021 bytes | 510.00 KiB/s, done.
Total 8 (delta 5), reused 0 (delta 0)
remote: Resolving deltas: 100% (5/5), completed with 5 local objects.
To github.com:Paramount-Software-Solutions/ebc-api.git
a5d33e6..d151083 dev -> dev


// IF there is no content in an upstream branch - the --dry-run shows the right command to push to a new branch

git push --atomic --dry-run
fatal: The current branch orders has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin orders


git push --set-upstream origin orders
Enumerating objects: 34, done.
Counting objects: 100% (34/34), done.
Delta compression using up to 8 threads
Compressing objects: 100% (23/23), done.
Writing objects: 100% (23/23), 3.63 KiB | 1.21 MiB/s, done.
Total 23 (delta 14), reused 0 (delta 0)
remote: Resolving deltas: 100% (14/14), completed with 11 local objects.
To github.com:Paramount-Software-Solutions/ebc-v2-api.git
   bbbd5c7..9ef52d3  orders -> orders
Branch 'orders' set up to track remote branch 'orders' from 'origin'.

==========================================
Begin session with git pull

Work on the files (I don't even do 'branches')

when finished, I run the shell script

echo "Insert git commit comments"

read COMM

git add -A

git commit -m "$COMM"

git push

it works fine

------------------
>> see what changes will be pushed 
------------------

git add -A

git commit --dry-run -m 'fix create device, trades jem'   

git push  --dry-run


------------------
output 

git commit --dry-run -m 'fix create device, trades jem'  
On branch dev
Your branch is up to date with 'origin/dev'.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	new file:   .vscode/launch.json
	modified:   package-lock.json
	modified:   package.json
	modified:   src/services/accounts/accounts.hooks.js
	modified:   src/services/devices/devices.hooks.js
	modified:   src/services/trades/trades.hooks.js
	modified:   yarn.lock


------------------
>> push changes normally when the ancestor is latest commit
------------------

git add -A

git commit -m 'fix create device, trades jem'   

git push 




git remote set-url origin https://github.com/Paramount-Software-Solutions/ebc-api.git


cat ~/.ssh/id_rsa.pub

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC3cyQ/Z32NT5E29pU3SK9zXaaiai0Oy1wEyki0A97YWh6LBtaOziQHnbbfZ/yzOF0Xg3aC2nc17g8nNy4oddDM8LZGRw0s+zntygaIQVsW539nribM+oSQrucQyass/dC4+8bUx0Brnn9iyBwQLWSQClzc6wt9tohbJp642Q854zYkj5cM84M0kajJsDW2sZpYWPezRN9DN0vWhnWxteroR62PFkqW4zBaW4keUEewQYGMUN/rl7jTspnfAwVrwdyJt4mGlUtIUYhFnsQoYrDDALDGrZmdt8x4JHIgQfq+caFNNdrlDhuc1j0wXR/nUXXYx5uiUWcJQAZUQdSqhupM6ltba/d/CXZSdH9yBLMGxQ20M6SRUfNitDgmnXZEn9a+dP4a8WLeIQ2kQtO6oqKsaoLBOSgG0zGCnb8Zrr/BEg0dWTjCIPU7FcvwkwrjnhY8jQk/AWD8AZS+ZOYwmmUzm4u0YPpJ4eqUWs+gTXTPf+5AKEAzZxHd/40FYCzICpE= jimmason@ip-10-0-0-103.us-east-2.compute.internal

https://github.com/settings/keys

git remote set-url origin git@github.com:Paramount-Software-Solutions/ebc-api.git


---------------
move to qa after dev>>
---------------

git checkout qa
git merge dev
git push


---------------
gen frontend for feathers 

marmalab v2 only for web sockets


---------------
call from 1 app to 2nd app i 


------------------
>> force the changes overriding other commits on origin 
------------------

git add -A --force 

git commit --dry-run --no-verify -m 'fix create device, trades jem'   

git push --force


------------------

------------------
git add 

This command updates the index using the current content found in the
       working tree, to prepare the content staged for the next commit. It
       typically adds the current content of existing paths as a whole, but
       with some options it can also be used to add content with only part of
       the changes made to the working tree files applied, or remove paths
       that do not exist in the working tree anymore.


------------------
git commit

https://git-scm.com/docs/git-commit

Create a new commit containing the current contents of the index and the given log message describing the changes. The new commit is a direct child of HEAD, usually the tip of the current branch, and the branch is updated to point to it (unless no branch is associated with the working tree, in which case HEAD is "detached" as described in git-checkout[1]).

The content to be committed can be specified in several ways:

by using git-add[1] to incrementally "add" changes to the index before using the commit command (Note: even modified files must be "added");

by using git-rm[1] to remove files from the working tree and the index, again before using the commit command;

-n
--no-verify
This option bypasses the pre-commit and commit-msg hooks. See also githooks[5].

--dry-run

The --dry-run option can be used to obtain a summary of what is included by any of the above for the next commit by giving the same set of parameters (options and paths).


------------------
git reset

If you make a commit and then find a mistake immediately after that, you can recover from it with git reset.




------------------
git push 

git push [--all | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
	   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-v | --verbose]
	   [-u | --set-upstream] [-o <string> | --push-option=<string>]
	   [--[no-]signed|--signed=(true|false|if-asked)]
	   [--force-with-lease[=<refname>[:<expect>]] [--force-if-includes]]
	   [--no-verify] [<repository> [<refspec>…​]]

DESCRIPTION
Updates remote refs using local refs, while sending objects necessary to complete the given refs.

You can make interesting things happen to a repository every time you push into it, by setting up hooks there. See documentation for git-receive-pack[1].

When the command line does not specify where to push with the <repository> argument, branch.*.remote configuration for the current branch is consulted to determine where to push. If the configuration is missing, it defaults to origin.

When the command line does not specify what to push with <refspec>... arguments or --all, --mirror, --tags options, the command finds the default <refspec> by consulting remote.*.push configuration, and if it is not found, honors push.default configuration to decide what to push (See git-config[1] for the meaning of push.default).

When neither the command-line nor the configuration specify what to push, the default behavior is used, which corresponds to the simple value for push.default: the current branch is pushed to the corresponding upstream branch, but as a safety measure, the push is aborted if the upstream branch does not have the same name as the local one.

-f
--force
Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it. Also, when --force-with-lease option is used, the command refuses to update a remote ref whose current value does not match what is expected.

This flag disables these checks, and can cause the remote repository to lose commits; use it with care.


--push-option=<option>
Transmit the given string to the server, which passes them to the pre-receive as well as the post-receive hook. The given string must not contain a NUL or LF character. When multiple --push-option=<option> are given, they are all sent to the other side in the order listed on the command line. When no --push-option=<option> is given from the command line, the values of configuration variable push.pushOption are used instead.

--receive-pack=<git-receive-pack>
--exec=<git-receive-pack>
Path to the git-receive-pack program on the remote end. Sometimes useful when pushing to a remote repository over ssh, and you do not have the program in a directory on the default $PATH.

--[no-]force-with-lease
--force-with-lease=<refname>
--force-with-lease=<refname>:<expect>
Usually, "git push" refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it.

This option overrides this restriction if the current value of the remote ref is the expected value. "git push" fails otherwise.



==========================================


------------------
usage: git [--version] [--help] [-C <path>] [-c <name>=<value>]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]

These are common Git commands used in various situations:

start a working area (see also: git help tutorial)
   clone     Clone a repository into a new directory
   init      Create an empty Git repository or reinitialize an existing one

work on the current change (see also: git help everyday)
   add       Add file contents to the index
   mv        Move or rename a file, a directory, or a symlink
   restore   Restore working tree files
   rm        Remove files from the working tree and from the index

examine the history and state (see also: git help revisions)
   bisect    Use binary search to find the commit that introduced a bug
   diff      Show changes between commits, commit and working tree, etc
   grep      Print lines matching a pattern
   log       Show commit logs
   show      Show various types of objects
   status    Show the working tree status

grow, mark and tweak your common history
   branch    List, create, or delete branches
   commit    Record changes to the repository
   merge     Join two or more development histories together
   rebase    Reapply commits on top of another base tip
   reset     Reset current HEAD to the specified state
   switch    Switch branches
   tag       Create, list, delete or verify a tag object signed with GPG

collaborate (see also: git help workflows)
   fetch     Download objects and refs from another repository
   pull      Fetch from and integrate with another repository or a local branch
   push      Update remote refs along with associated objects

'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
See 'git help git' for an overview of the system.


NODE_ENV=devLocal  PORT=3030   npm start


==========================================
vscode debug 
==========================================

open debug terminal
set code breakpoints
when running to breakpoint
view variables in a watchlist
or hover over variable to view attributes


context is the default object for a request contains
app.(req,res, next)
arguments
data ( from post )
variables from cdm lin as a key map
params ( if entered on the request )
path ( the relative url )
service ( service properties for the feathers service )
toJSON ( normally empty )
type:  ( feathers request life cycle - before or after )
__proto__ ( the object prototype if defined )


in debug console, enter debug commands

console.log(`context.data : ${JSON.stringify(context.data)} \n`);
undefined
context.data : {"offerKWH":"120","rate":0.5,"startTS":"2021-02-28T07:21","endTS":"2021-07-04T07:21"} 


==========================================
create PR to merge code to another branch
==========================================

given DEV latest version, 
create PR to merge from DEV to QA

To request that changes from your branch are merged into another branch, in the same repository or in another repository in the network, you can create a pull request on GitHub Desktop


-------------------------

commit latest to dev branch

compare fend dev to qa

https://github.com/Paramount-Software-Solutions/ebc-frontend/commit/5eb47481d15a743dc4d382662983e68ff46b1a3f

qa
https://github.com/Paramount-Software-Solutions/ebc-frontend/commit/7e6c780a3f68f295ca3226d5cd6f2c905e00795b


hard-coded constants file 
not using NODE_ENV like ebc-api

https://github.com/Paramount-Software-Solutions/ebc-frontend/compare/7e6c780a3f68f295ca3226d5cd6f2c905e00795b..5eb47481d15a743dc4d382662983e68ff46b1a3f

;
 API_URL = 'https://ebc-api-dev.sysopsnetwork.com/';

API_URL = 'https://ebc-api-qa.sysopsnetwork.com/';

==========================================
==========================================